You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently in all the packages we've defined build_requires for the build requirements, however in most scenarios this isn't actually correct as only the building of that package X itself requires those and not necessarily any packages that depend on X requires those too for building, as such those would be private_build_requires for X.
If package X requires cmake to run the build script then any dependent package does not need cmake, e.g. package Y might just build using make or sconstruct
If package X requires visualstudio to build but another does not then this could be private_build_requires.
Only whenever the dependent packages is required to build against it, e.g. when project Y headers link to project X headers then to build project Z that links Y it requires the headers of X too.
Z <---- Y <---- X
links links
The text was updated successfully, but these errors were encountered:
Issue
Currently in all the packages we've defined
build_requires
for the build requirements, however in most scenarios this isn't actually correct as only the building of that package X itself requires those and not necessarily any packages that depend on X requires those too for building, as such those would beprivate_build_requires
for X.See: https://github.com/nerdvegas/rez/wiki/Building-Packages#build-time-dependencies
As example:
cmake
to run the build script then any dependent package does not needcmake
, e.g. package Y might just build usingmake
orsconstruct
visualstudio
to build but another does not then this could beprivate_build_requires
.The text was updated successfully, but these errors were encountered: