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

[Qt5] Update Qt latest to 5.14.1 #10009

Closed
wants to merge 133 commits into from

Conversation

Neumann-A
Copy link
Contributor

@Neumann-A Neumann-A commented Feb 10, 2020

follow up PR to #9860. Made latest default feature to test CI run.
Needs testing against ParaView PR #9960 to make sure that everything is linked in correctly. But if ParaView builds with it, it should generally work with everything
Done testing Paraview builds and runs fine with Qt 5.12.7 and Qt 5.14.1

closes #10344
closes #10338

@Neumann-A
Copy link
Contributor Author

@longhuan2018: Triplet ?; Linked Qt5 CMake target? Are you using [latest] feature or are you building 5.12.7? I am currently testing building paraview with this PR on windows.

@longhuan2018
Copy link
Contributor

longhuan2018 commented Mar 11, 2020

@longhuan2018: Triplet ?; Linked Qt5 CMake target? Are you using [latest] feature or are you building 5.12.7? I am currently testing building paraview with this PR on windows.

I am using latest, and I also upgraded it to 5.14.1, just by modifying the hash value. But I am not based on this PR

@Neumann-A
Copy link
Contributor Author

@longhuan2018: Ok if you are not using this PR please don't mention linkage errors. This PR has additional patches to the Qt5XXXConfig.cmake.in to [latest] to fix the linkage. The reason you see those linkage problems is that _populate_UiTools_target_properties(DEBUG "Qt5UiToolsd.lib" "" FALSE) is called with the last argument being set to FALSE. This eliminates the required generator expression in the INTERFACE_LINK_PROPERTIES.

@longhuan2018
Copy link
Contributor

@longhuan2018: Ok if you are not using this PR please don't mention linkage errors. This PR has additional patches to the Qt5XXXConfig.cmake.in to [latest] to fix the linkage. The reason you see those linkage problems is that is called with the last argument being set to FALSE. This eliminates the required generator expression in the INTERFACE_LINK_PROPERTIES._populate_UiTools_target_properties(DEBUG "Qt5UiToolsd.lib" "" FALSE)

_populate_UiTools_target_properties

OK, then I will also use this PR to test my program

@Neumann-A
Copy link
Contributor Author

@longhuan2018 : Just remove the FATAL_ERROR and additional CI code add the end of the qt5-base portfile.cmake or you won't get far currently ;) (I require some files from ci check them for each platform once)

@JackBoosY
Copy link
Contributor

JackBoosY commented Mar 12, 2020

That's really a hard work, thanks!

@JackBoosY
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Pull request contains merge conflicts.

1 similar comment
@azure-pipelines
Copy link

Pull request contains merge conflicts.

# Conflicts:
#	scripts/ci.baseline.txt
…feature

# Conflicts:
#	ports/qt5-activeqt/CONTROL
#	ports/qt5-base/CONTROL
#	ports/qt5-gamepad/CONTROL
#	ports/qt5-graphicaleffects/CONTROL
#	ports/qt5-networkauth/CONTROL
#	ports/qt5-purchasing/CONTROL
#	ports/qt5-remoteobjects/CONTROL
#	ports/qt5-sensors/CONTROL
#	ports/qt5-serialport/CONTROL
#	ports/qt5-tools/CONTROL
#	ports/qt5-webchannel/CONTROL
#	scripts/ci.baseline.txt
@JackBoosY
Copy link
Contributor

/azp run

@JackBoosY
Copy link
Contributor

Oh, this PR exists so long...

@JackBoosY
Copy link
Contributor

/azp run

@Neumann-A
Copy link
Contributor Author

outdated 5.14.2 released

@Neumann-A Neumann-A closed this Apr 1, 2020
@Neumann-A Neumann-A deleted the update_qt_latest_5_14_1 branch April 27, 2020 21:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

qt5[latest] update to 5.14.1 [qt5-imageformats] build failure
4 participants