-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
[qt5-base] Fix Qt5 linux build and be a bit less flaky in CI #9260
Conversation
fixes some observed linkage issues
…o fix_qt_linux
There was also an issue with linkage of expat. Have to find the port linking to it |
will add the following fixes described here as soon as i have time: |
/azp run |
So I included every fix I know of in this PR. ah ok #9299 still needs fixing |
Seems there are two problems with Qt that worth to note. On
while on
And the major one: there is no "direct" way to link static Qt from cmake (no targets for plugins and additional libraries(Qt5ThemeSupport), dependencies(external, internal) not declared). So |
next issue: _populate_Core_plugin_properties only populates release properties |
hmm seems like fixcmake.py is not 100% doing what it should be
|
@janholt: Your issue should be solved now |
If you have completed this fix, please let me know. Thanks. |
Also VTK should build on linux. The error is:
so the CI machine is missing some required system library |
Confirmed. |
Hello, |
@zweistein-frm2: If you cannot wait until this is merged into master:
|
OK, almost there, takes 6-12 h to compile on linux and goes through |
Seems that the database corruptions occurred only on a Windows and WSL install. On a real Ubuntu 18.04 there are no problems |
Maybe related: The windows vcpkg and the WSL vcpkg directories point to the same folder. Should be fine? as the triplets are in seperate folders |
Yep the reason is:
No its not fine. vcpkg is not designed to be run in parallel into the same installed folder. This typically corrupts the database located in the folder |
find_library(${_lib}_LIBRARY_RELEASE NAMES ${_lib} PATH_SUFFIXES plugins/platforms) | ||
set_property(TARGET ${_target} APPEND PROPERTY INTERFACE_LINK_LIBRARIES | ||
\$<\$<NOT:\$<CONFIG:DEBUG>>:${${_lib}_LIBRARY_RELEASE}>\$<\$<CONFIG:DEBUG>:${${_lib}_LIBRARY_DEBUG}>) | ||
#The fact that we are within this file means we are using the VCPKG toolchain. Has such we only need to search in VCPKG paths! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
You're 100% correct, but just to be very verbose about it:
So it's ok to open a windows prompt, run |
/azp run |
/azp run |
No description provided.