The way I usually work is to run aliBuild once, then cd into the build tree and then simply enter a typical development loop : edit code; ninja && ctest; edit code; ninja …
Usually ninja (and the cmake it reruns only when needed) takes a fraction of time (because each code edit phase is focused on a very limited number of files, most often only one, so the build only deals with a handful of files) and all is good.
But sometimes the rebuild is jumping to rebuild hundred of files, for no apparent reason (well, there must be a reason, but so far I failed to identify it). What’s worse, in those cases the build fails with :
ld: warning: directory not found for option ‘-L/lib’
ld: warning: directory not found for option ‘-L/lib’
ld: library not found for -lG4clhep
and then my way out is to scratch the build tree and start again, which is of course very disrupting.
Has anyone else experience such issue ? Any idea what the cause might be ?
I’ve observed this on macOS for sure, not quite remember if it ever happened on CentOS (which is not my go-to dev platform).
Thanks, and sorry for what I realize is a very vague bug report…
Since a few weeks this has error has been the standard on my laptop after pulling dev branch or after a git checkout on a different branch. Deleting GEANT4 build and rebuilding with AliBuild solves the problem temporarily.
@laphecet, any ideia of what’s causing this? Not a big deal, though.
No idea for the moment. Unfortunately I’ve not investigated yet (as I have been developing lately under o2-dataflow where the issue is not present )
But it’s not forgotten.