-
Notifications
You must be signed in to change notification settings - Fork 972
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] conan export-pkg has seemingly all values from profile propagated with the exception of CONAN_CMAKE_GENERATOR #4832
Comments
hi @trondhe, Could you please share here the code in the I do not understand why the export-pkg is conditional to Thanks! |
The setup is identical with another issue I had, and this error appeared when I solved it, as you said by having It was maybe a bit badly explained, but the issue appears when executing |
Will try to reproduce the error. Thanks for the details! |
I have submitted a PR in #4852 trying to solve this issue. |
Merged, will be released in next Conan 1.14, please try then and report. Thanks |
When I want to export to local cache from a local source dir, I first run the setup commands and build my project
then when I run either of these commands the wrong generator is used
Looking at the
command
variable at line 195 in the cmake.py cmake helper class, the command given to cmake is exactly the same for both versions ofexport-pkg
above. The cmake command value is how I expect it to be with the exception of that the generator given in the profile is not respected, but uses the default given in conan.conf. If no default in conan.conf is given it defaults back to MinGW Makefiles.A workaround is to set the correct generator as default in conan.conf. But this can only be temporary as projects sometimes includes C# so a mix of generators is to be used.
The text was updated successfully, but these errors were encountered: