How to upload build dependencies too?
See original GitHub issueI have a package A
which has other packages (e.g. B
) as build dependencies. Package B
is not available as a binary package. When I build A
with build_policy
set to missing
package B
is build from source as well.
At the end the new package for A
is uploaded to my repo. Is it possible to automatically upload the new package for B
as well?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:6
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Adding package dependencies to your app - Apple Developer
After you choose a package requirement, Xcode resolves and fetches the package dependency. Select the package's products that you need, and add them...
Read more >Manage build dependencies | Netlify Docs
Specify dependencies for your project so that our platform can install required languages and software before running a build.
Read more >Ideas for speeding up installing dependencies - Stack Overflow
1 Answer 1 ; a - download them from outside servers - at every build ; b - build them from repo sources...
Read more >How to Upload Your Python Package to PyPI and pip
How to make your Python package available on PyPi · Step 1: Ensure you have pip installed · Step 3: Package your Python...
Read more >TeamCity On-Premises - Build Dependencies Setup - JetBrains
Build Dependencies Setup · Compile your project. · Run tests under Windows and macOS simultaneously on the same sources. · Build a release...
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 FreeTop 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
Top GitHub Comments
Hah, while my first instinct is that it’s better to have a dedicated job to build B separately, while thinking about it, I definitely noticed the temptation. As bincrafters, we could define one job “boost_all” with build missing, and let the whole boost tree be built (and now uploaded) recursively. I still don’t think it’s a good idea in our case, has lots of impracticalities at scale, but now I can see it being worthwhile in some cases. For example, if you are setting up CPT for a small new project, and building a few unique combination of settings/options for which there are no binaries in conan center, and use an OSS package which has 10 dependencies. It would be tedious to have to setup a CI job to build each separately.
We also need this feature. I might be able to contribute it but need some advice on how to implement it. Would you envision this as an option of the
conan upload
command? If so, wouldn’t we need two options: (1) upload transitive runtime dependencies and (2) upload transitive build dependencies?