Set data packages variables only for build/test environment
The way data packages environment variables were propagate to downstream projects was breaking relocatability of builds, in particular for nightly builds and satellite projects.
With this change the data packages environment is only set for build and tests, but not propagated to the .xenv
file as anyway lb-run
takes care of actual lookup and environment of data packages for the runtime.
The only doubt I have is that an old style cmake project will not be able to inherit the data package environment from a new style upstream project, but it's not so clear if it is a relevant use case (the trivial workaround is to modify the old project to depend on the data package, which is anyway a good idea).
@cattanem, this fixes (in principle) the issue you reported about the wrong $PRCONFIGROOT
.
Merge request reports
Activity
added lhcb-gaudi-head label
- [2021-07-06 00:04] Validation started with lhcb-gaudi-head#2979
- [2021-07-07 00:05] Validation started with lhcb-gaudi-head#2980
Edited by Software for LHCbmentioned in commit eb65a4b0
@clemenci For my information is this going to work also when running from an
lb-dev
build? Because there are users that do that...mentioned in commit Moore@26b82ffb
mentioned in merge request Moore!921 (merged)
mentioned in commit Moore@2800dc9c
mentioned in commit Allen@f0beccd8
mentioned in merge request Allen!604 (merged)
mentioned in commit MooreAnalysis@bfb844c7
mentioned in merge request MooreAnalysis!40 (merged)
mentioned in commit MooreAnalysis@53232a9f
mentioned in commit Allen@764a66af
mentioned in merge request lhcb-core/LbEnv!118 (merged)