-
Notifications
You must be signed in to change notification settings - Fork 992
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
[bug] Creating zlib-ng
package for WindowsStore
and armv8
#17589
Comments
zlib-ng
Recipe for WindowsStore
and armv8
zlib-ng
package for WindowsStore
and armv8
Hi @karel-tomanec - if I understand correctly, the question is how to set that policy such that CMake avoids choosing the most recent Windows SDK version? Could you post a log of the successful creation of the Additionally,
I would advise to not invoke Conan from an already initialised visual studio developr command prompt - this means that the windows SDK version is already chosen and activated in the environment, and those environment variables are exposed to anything Conan invokes (cmake, msbuild), which can cause issues - doing this is not necessary:
|
Hi @jcar87, Apologies for the confusion earlier. I’ve updated the logs to reflect the situation where the package is not downloaded from the remote. Regarding my workaround, it forces CMake to select the toolchain without including the version field, as the version field seems to cause issues for some reason. Here’s the relevant snippet:
|
Describe the bug
Hi,
I am working on creating a
zlib-ng
package foros=WindowsStore
andarch=armv8
. I modified the officialzlib-ng
recipe in this PR.Below is the command I used to create the package and the following log:
Click to expand log
Initially, the process failed due to an error in the compiler check. I updated the generate method to include the following workaround:
Click to expand recipe
and tried to create a package as before:
Click to expand log
After applying this change, the package was created successfully. However, the test package failed, which I assume is due to cross-compilation limitations. This was expected.
Question:
Is there a better way to address this issue without modifying the generate method of every recipe? The current workaround involves injecting a custom CMake policy (CMP0149) into the toolchain file, which feels cumbersome and error-prone, especially when applied to multiple recipes.
Thank you for your assistance!
Package and Environment Details
The text was updated successfully, but these errors were encountered: