-
Notifications
You must be signed in to change notification settings - Fork 1
Home
Sylvain Joyeux edited this page Dec 8, 2017
·
2 revisions
- there is no way to add a folder to the workspace through the API, and therefore some functionalities (like the add/remove folder events) can simply not be tested. Best practice is to move as much code as possible out of the VSCode loop into functions that can be tested separately.
- tasks are identified through their definition field, which means that two task objects that have the same definition will end up showing only once in the build target list.
- if you rename or remove a test file, you would need to remove them from the out/ folder as well, or the test runner will continue running them.
- if env.sh is not loaded, running
<workspace_root>/.autoproj/bin/autoproj
with the working directory at the root gives you autoproj services. theexec
subcommand runs a subcommand, setting the environment first. - there is a JSON file with info on directories of the packages in
<workspace_root>/.autoproj/installation-manifest
. This is how acd/alocate are much faster than the other tools (they don't need to load the whole configuration). - the build folder of a package cannot be assumed to be
<package_srcdir>/build
. Discover with eitheralocate -b
or through the installation-manifest. The prefix is eitheralocate -p
, or discovered from the installation manifest.