The model where nimbus-build-system.paths were generated as a dependency
from `update-common` proved to create various issues in practice:
* It was not working properly during the repository bootstrapping
because the paths file generation script is assuming that all
submodules are already checked out
* It was not always triggered from builds of the top-level targets
due to missing or already satisfied dependencies on `update-common`.
A more proper solution would structure the dependencies like this:
top-level-project -> nimbus-build-system.paths -> vendor-modules
... but this requires a larger refactoring of the Makefiles, so I'm
merging this interim solution as a way to improve the status quo.
Scripts sourcing a project env.sh file (e.g. direnv's .envrc) can specify
the `NBS_ONLY_LOAD_ENV_VARS` env variable to avoid any attempts from NBS
to execute a target script. Previously, the script was trying to detect
only sourcing from an interactive shell.
Here POC on what are the other steps that have to be performed to allow using NBS.
0961d3acc2
Once all projects migrate to this approach, the code related to building
NIMBLE_PATH can be deleted from the repo
cc @zah
I'm using this directory as a place to put the new testrunner exe
from the testutils package. For now, I'm doing this manually, but
it may be automated by the Makefiles in the future.
Zahary Karadjov
Jacek Sieka
Ivan Yonchovski
Ștefan Talpalaru
Jakub
Zahary Karadjov