Closed doudou closed 6 years ago
STATUS SO FAR
autoproj which
subcommand).One provides a program path relative to the build, source or prefix dir. The extension resolves it. I think I'll change it to rather expand variables like `${autoproj:buildDir} instead, which would make it explicit.
This handles C++ and Ruby debug configurations in
launch.json
to allow running them within a Rock workspace transparently.Behind the scenes, the extension now starts all the debugged processes using the workspace's environment (using
autoproj exec
)In addition, the extension provides four variable expansions that can be used within
launch.json
in theprogram
andcwd
fields of the debug configurations:${rock:srcDir}
expands to the package's source directory${rock:buildDir}
expands to the package's build directory${rock:prefixDir}
expands to the package's prefix directory${rock:which:_cmd_}
expands to the result ofautoproj which _cmd_
as run within the workspace, i.e. solves the full path to_cmd_
with thePATH
of the workspace.For instance, a Ruby
rake test
configuration would be:a C++
Run Rock's default test suite
would be: