Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

drop qmake #58

Open
AndreiCherniaev opened this issue Feb 12, 2024 · 8 comments
Open

drop qmake #58

AndreiCherniaev opened this issue Feb 12, 2024 · 8 comments
Labels
enhancement New feature or request

Comments

@AndreiCherniaev
Copy link
Contributor

AndreiCherniaev commented Feb 12, 2024

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

  • Please use the 👍 reaction to show that you are interested into this.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this.
  • Subscribe to receive notifications on status change and new comments, you can do also without add comment.
@AndreiCherniaev AndreiCherniaev added the enhancement New feature or request label Feb 12, 2024
@bigbigmdm
Copy link
Owner

@AndreiCherniaev I only use CMake. The .pro files are only needed for my QT5 Creator. (Not used for builds).

@bigbigmdm
Copy link
Owner

They are included in .gitignore. Since I use two computers in different locations for now I am comfortable storing .pro files on GitHub.

@AndreiCherniaev
Copy link
Contributor Author

AndreiCherniaev commented Feb 12, 2024

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

@bigbigmdm
Copy link
Owner

Yes, i thing it, but it is historical

@AndreiCherniaev
Copy link
Contributor Author

AndreiCherniaev commented Feb 12, 2024

Yes, i thing it, but it is historical

Если что я ваши проекты так и открываю в кьюти креэторе:
File > Open file or project
select
CMakeLists.txt

А из-за того что у вас .pro файлы лежат путаница возникнет, да и вы сами запутаетесь, когда у вас в креэторе проект будет собираться и работать одним образом, а через CMake собираться и работать другим образом. Или вообще не собираться... Настоятельно рекомендую избегать путаницы, то есть удалить .pro

AndreiCherniaev added a commit to AndreiCherniaev/IMSProg_fix that referenced this issue Apr 13, 2024
AndreiCherniaev added a commit to AndreiCherniaev/IMSProg_fix that referenced this issue Apr 13, 2024
@bigbigmdm
Copy link
Owner

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.
341-347
Today it can only detect the presence of the CH347 programmer...

@AndreiCherniaev
Copy link
Contributor Author

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.
Screenshot from 2024-07-03 14-05-08
Screenshot from 2024-07-03 14-03-22

@bigbigmdm
Copy link
Owner

bigbigmdm commented Jul 3, 2024

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants