-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[qt6] Add support for MACOSX_BUNDLE #24642
[qt6] Add support for MACOSX_BUNDLE #24642
Conversation
This comment has been minimized.
This comment has been minimized.
Signed-off-by: Uilian Ries <uilianries@gmail.com>
c317115
to
adf3e57
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
recipes/qt/6.x.x/conanfile.py
Outdated
@@ -837,6 +839,8 @@ def package(self): | |||
filecontents += f"set(QT_VERSION_MAJOR {ver.major})\n" | |||
filecontents += f"set(QT_VERSION_MINOR {ver.minor})\n" | |||
filecontents += f"set(QT_VERSION_PATCH {ver.patch})\n" | |||
if self.settings.os == "Macos": | |||
filecontents += f'set(__qt_internal_cmake_apple_support_files_path "{os.path.join(self.package_folder, "res", "macos")}")\n' |
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.
does this not cause a file inside package_folder
to have a full, absolute path referencing a file that existed at package build time, but may not exist on a different computer? intuitively this should be a relative path?
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.
Agreed, it should be relative path. Absolute will break users for sure.
This comment has been minimized.
This comment has been minimized.
Hooks produced the following warnings for commit e19a3deqt/6.7.1@#01499e0b39e277ad24155decbb7791cb
qt/5.15.14@#363b63b84714e9a9b3f108e8382468ed
qt/6.6.3@#30113cee42cf1ae31f805f7ae19a79f3
qt/6.5.3@#25be311dd23e5cdcde10ac95b96e1cc8
|
Changed as draft to fix the cmake relative path when consuming the package. |
Signed-off-by: Uilian Ries <uilianries@gmail.com>
@jcar87 I changed the recipe use the relative path instead: 3f6b361 I tested locally using the follow patch for test package: The full build log is this one: |
Conan v1 pipeline ✔️All green in build 7 (
Conan v2 pipeline ✔️
All green in build 5 ( |
Hooks produced the following warnings for commit 3f6b361qt/5.15.14@#bc8373cc091c60c28bccd10d055a8ac1
qt/6.7.1@#e613f59c8895e27caca9f42ffa05bda6
qt/6.6.3@#d6ad1c1822d9de56fbf1ebccc6b3e4af
qt/6.5.3@#b32599d5df35abba037b7b54f6c7a64e
|
Summary
Changes to recipe: qt/6.7.1
Motivation
The Qt project exports more files and variables than CMakeDeps. The variable
__qt_internal_cmake_apple_support_files_path
is consumed to point whereInfo.plist.app.in
should be installed.Details
To validate the current change, I modified the test package to use
qt_add_executable(${PROJECT_NAME} MACOSX_BUNDLE test_package.cpp)
:Content of
Info.plist.app.in
Build test log:
fixes #20574
/cc @tamaskenezlego @DoomHammer