options with * are not applied to the root package
See original GitHub issueExample:
I want to install some modular Boost package which requires other Boost packages. I want all of them to be shared. The intuitive command would be
conan install Boost.Test/1.65.1@user/testing -o Boost.*:shared=True
But that installs only the requirements shared, the main package (Boost.Test) is static. To avoid that, I need to do
conan install Boost.Test/1.65.1@user/testing -o Boost.*:shared=True -o shared=True
Is that the intended behaviour? If so, I would at least add a warning in the docs.
Conan 1.0.3, Windows
- I’ve read the CONTRIBUTING guide.
- I’ve specified the Conan version, operating system version and any tool that can be relevant.
- I’ve explained the steps to reproduce the error or the motivation/use case of the question/suggestion.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
'package.json' is not under 'rootDir' - Stack Overflow
solution: use separate Typescript sub-projects · Give the src dir its own project. ./src/tsconfig.json : · Give the root dir its own project....
Read more >Troubleshooting NuGet Package Restore in Visual Studio
Set both options under Package Restore. ... the error means that the package is not installed in the packages folder at the solution...
Read more >Shared Options | Vite
If you have duplicated copies of the same dependency in your app (likely due to hoisting or linked packages in monorepos), use this...
Read more >package.json - npm Docs
Description. This document is all you need to know about what's required in your package.json file. It must be actual JSON, not just...
Read more >Content roots | IntelliJ IDEA Documentation - JetBrains
From the main menu, select File | Project Structure Ctrl+Alt+Shift+S and click Project Settings | Modules. · Select the necessary module and then...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Before to read your comment I collected some new information.
Running boost_level8group/1.66.0@bincrafters/testing on lasote/conangcc6
package_id was collected by
self.info.package_id() self.options.values.sha was collected by
self.options.values.shaself.settings.values.sha was collected by
self.settings.values.sha`Now I chose two results to compare:
Both uses the same settings, but the options are not the same. The package id is the same for both two. Looks like when options contains
*
the package id skip it on append.I used the latest Conan version (1.0.3)
FYI, we’ve worked around it. Our shared code for building the boost packages with
conan-package-tools
now passes both shared options when building. Whenever it gets patched in conan, great… but it’s not blocking us at the moment.