-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Do not pass -DQT_REQUIRE_HOST_PATH_CHECK=OFF in cross-compiled builds #279
base: qt6
Are you sure you want to change the base?
Conversation
I did not bumped the build number as this is a cleanup meant to be included in the next actual build. |
hmm, these "include in the next build" have been very hard to sync up. |
If prefer I can bump the build number, feel free to let me know what do you prefer. |
yeah, just bump the build number and merge from the qt6 branch before you do. that way this fix gets in. |
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
@conda-forge-admin, please rerender |
Done! |
…nda-forge-pinning 2024.08.10.13.11.06
Hi! This is the friendly conda-forge automerge bot! Commits were made to this PR after the |
does this PR resolve #273? |
No, it cleans up a previous attempt to fix the issue, that did not do what was intended to do. |
The |
restarted |
Hi! This is the friendly conda-forge automerge bot! I considered the following status checks when analyzing this PR:
Thus the PR was not passing and not merged. |
As explained in #273 (comment), the PR #274 did not actually solved #273 .
While having a proper fix would be convenient, I am not sure how to do that, so in the short term the best action is to cleanup the recipe, and continue to track the problem in #273 .
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)