Files
src
Folders and files
Name | Name | Last commit date | ||
---|---|---|---|---|
parent directory.. | ||||
This directory contains the QT project required for compiling MCP2210 Configurator. A list of relevant files follows: – aboutdialog.cpp; – aboutdialog.h; – aboutdialog.ui; – common.cpp; – common.h; – configuration.cpp; – configuration.h; – configurationreader.cpp; – configurationreader.h; – configurationwriter.cpp; – configurationwriter.h; – configuratorwindow.cpp; – configuratorwindow.h; – configuratorwindow.ui; – icons/active64.png; – icons/buttons/password-reveal.png; – icons/buttons/password-reveal.svg; – icons/greyed64.png; – icons/icon.svg; – icons/mcp2210-conf.png; – icons/selected64.png; – images/banner.png; – images/banner.svg; – libusb-extra.c; – libusb-extra.h; – main.cpp; – mainwindow.cpp; – mainwindow.h; – mainwindow.ui; – mcp2210-conf.pro; – mcp2210.cpp; – mcp2210.h; – mcp2210eeprom.cpp; – mcp2210eeprom.h; – mcp2210limits.h; – misc/mcp2210-conf.desktop; – passworddialog.cpp; – passworddialog.h; – passworddialog.ui; – resources.qrc; – statusdialog.cpp; – statusdialog.h; – statusdialog.ui; – translations/mcp2210-conf_en.qm; – translations/mcp2210-conf_en.ts; – translations/mcp2210-conf_en_US.qm; – translations/mcp2210-conf_en_US.ts; – translations/mcp2210-conf_pt.qm; – translations/mcp2210-conf_pt.ts; – translations/mcp2210-conf_pt_PT.qm; – translations/mcp2210-conf_pt_PT.ts. In order to compile successfully, you must have the packages "build-essential", "libusb-1.0-0-dev" and "qt5-default" (or "qtbase5-dev") already installed. Given that, if you wish to simply compile, change your working directory to the current one on a terminal window, and invoke "qmake", followed by "make" or "make all". Notice that invoking "qmake" is necessary to generate the Makefile, but only needs to be done once. You can also install using make. To do so, after invoking "qmake", you should simply run "sudo make install". If you wish to force a rebuild before the installation, then you must invoke "sudo make clean install" instead. It may be necessary to undo any previous operations. Invoking "make clean" will delete all object code generated during earlier compilations. However, the previously generated binary is preserved. It is important to note that it is possible to undo previous installation operations as well, by invoking "sudo make uninstall". Such approach is not recommended, though. P.S.: Notice that any make operation containing the actions "install" or "uninstall" (e.g. "make install" or "make uninstall") requires root permissions, or in other words, must be run with sudo.