-
Notifications
You must be signed in to change notification settings - Fork 15
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
Cura 8640 PyQt6 upgrade #17
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
These allow for a uniform way of handling rpath, threads etc. Contributes to CURA-8640
Although not needed at run-time, it is needed for freeze time, such that cx-freeze can find it. Contributes to CURA-8640
Contributes to CURA-8640
../lib is an symlink to ../Resources/lib/ Contributes to CURA-8640
Contributes to CURA-8640
Contributes to CURA-8640
Contributes to CURA-8640
Contributes to CURA-8640
Contributes to CURA-8640
We don't want to set a new variable with as name the current PYTHONPATH. We want to set the PYTHONPATH itself. Contributes to issue CURA-8640.
…RA-8640_PyQt6_upgrade
Contributes to CURA-8640
Contributes to CURA-8640
Contributes to CURA-8640
Contributes to CURA-8640
Contributes to CURA-8640
Contributes to CURA-8640
Contributes to CURA-8640
Contributes to CURA-8640
Contributes to CURA-8640
This was referenced Apr 12, 2022
This was referenced Apr 12, 2022
2 tasks
Ghostkeeper
suggested changes
Apr 13, 2022
Contributes to CURA-8640
Allready taken care of in StandardProjectSettings Contributes to CURA-8640
codestyle Contributes to CURA-8640
BUILD_STATIC was our own custom option while BUILD_SHARED_LIBS is a global CMake flag Contributes to CURA-8640
Contributes to CURA-8640
Ghostkeeper
approved these changes
Apr 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Because we are switching to Qt6 we also needed to update SIP to 5.0+
SIP5+ builds en generate the code using a new process and executable. We had a lot of trouble linking the sip generated binaries on all three systems using the QGIS CMake Macro's so we decided to let sip only generate the C++ source code from the sip files and leave compiling and linking in the CMake domain. This is achieved by using our own CMakebuilder.py which is then used by sip-build instead of its shipped builder. This Cmakebuilder is basically the same in every respect except the call to the build function has been removed.
Make sure that sip-build is installed and that it is added to the PYTHONPATH
In order to get this to work on our build-system and working for all three OSes we did a shit tons of boy scouting in our cmake. We removed old methods with variables and try to be consisted in a target-based approach. The idea is that we don't patch stuff down the line, but that the install should place everything with desired rpaths for each project.
Removed the find_packages for the C++ libraries, since these fall outside of the responsibility of a consuming project in general, especially since these dependencies output their own find_package module. Just make sure the
CMAKE_PREFIX_PATH
is set correctly and if that fails the<Packagename>_ROOT
should point to the correct root folder of that dependency.Part of
Fixes
Todo