Implementation of layered LCG software stacks
Compare changes
Files
3+ 112
− 0
2. Building the full stack is done using the sub-command `install`. If no target is specified then the top level packages, declared with `LCG_top_packages`, and their dependencies will be downloaded if the binary already exists for this exact platform and exact list of version of the dependencies or build locally.
Additional functionality has been added to the `lcgcmake` tool for supporting the use case of developing a package within the stack. In this case the user should be able to indicate the location of the new sources for the package being developed instead of using the official source tarfiles. This is done by either providing a git repository or by the full path to a source directory. The toolchain file can be modified as follows:
In this example we have taken ROOT and DD4hep but it can be any other package or set of packages. You need to base the development on a give full release, then you overwrite the desired package[s] pointing to your [forked] repository or local checkout area. The version is used a 'tag' for the GIT repository and is ignored for the local checkout area.