...
The files comprising the SCons machinery are of different types and reside in different places:
- package-specific For each package there must be a file called SConscript. For packages building libraries there must also be a file pkgName_Lib.py. Both are in the package root directory
- global, container-specific The file package.scons and the file externals.scons, kept in the top-level directory of the container
- global, generic These files are identical for all containers. Only a single copy is kept in CVS (under SConsFiles). This category includes the files SConstruct, processExternals.scons, allExternals.scons and several tools in site_scons/site_tools
...
There are includes under healpix/src which, though not directly referenced as public include files, are themselves included by public include files. This causes problems when building with SCons since, when building a package, SCons expects mapall required includes not belonging to that package to be in the install area. skymaps needs access to such a hidden include. The work-around has been to add lines like the following to skymaps SConscript:
Wiki Markup
but this won't work for asp_skymaps since the # refers to the root of the ScienceTools installation (because that's where SConstruct is) and asp_healpix, which is what asp_skymaps should be using, lives under ASP.
...
This built without error and installed libraries libBayesianBlocks.so and lib_BayesianBlocks.so, but when running python/test_BayesianBlocks.py
- failure of line import BayesianBlocks. There is a file build/<variant>/source/BayesianBlocks.py which is presumably the right file, but it isn't installed anywhere. Temporary work-around was to copy it to python directory
- in file BayesianBlocks.py failure of import _BayesianBlocks Work-around was to change line to import lib_BayesianBlocks.
- unable to find liboptimizers.so This is because of problem with _setup described above. The file exists in ST lib directory.
...