Open AndreiCherniaev opened 5 months ago
@AndreiCherniaev I only use CMake. The .pro files are only needed for my QT5 Creator. (Not used for builds).
They are included in .gitignore. Since I use two computers in different locations for now I am comfortable storing .pro files on GitHub.
They are included in .gitignore. Since I use two computers in different locations for now I am comfortable storing .pro files on GitHub.
But .pro files no need to work in Qt Creator. Qt Creator can works with CMake projects. File > Open file or project select CMakeLists.txt
Yes, i thing it, but it is historical
Yes, i thing it, but it is historical
Если что я ваши проекты так и открываю в кьюти креэторе: File > Open file or project select CMakeLists.txt
А из-за того что у вас .pro файлы лежат путаница возникнет, да и вы сами запутаетесь, когда у вас в креэторе проект будет собираться и работать одним образом, а через CMake собираться и работать другим образом. Или вообще не собираться... Настоятельно рекомендую избегать путаницы, то есть удалить .pro
This is a secondary objective. Especially since I use these files when using QTCreator. Neither Debian nor RedHat Developers are embarrassed by their presence. There is a much more interesting task that I can't get to - adding support for the CH347T programmer. I need both strategic advice and help here.
Today it can only detect the presence of the CH347 programmer...
Especially since I use these files when using QTCreator.
Please use CMakeLists.txt to open project in Qt Creator. If you will open CMakeLists.txt then Qt Creator will use CMake build system.
@AndreiCherniaev , I'm not convinced. I am not comfortable installing intermediate versions in /usr/bin. So I have to make two CMakeLists.txt - one for the release, one for myself. That's even more ugly.
Description
Looks like you use CMake and qmake both build systems. But looks like you prefer CMake. I think it is good choice! Do you really need qmake? It will take a great power to keep up to date both. I suggest drop qmake (remove IMSProg_editor.pro and IMSProg.pro).
Usage tips