You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the cb command allows passing custom options to colcon build through the environment variable $CB_EXTRA_ARGS. It would be nice to be able to just append the desired build options directly after the cb command.
This can be done by shifting the workspace argument and passing the reminder "$@" to the colcon build command.
This feature should also be combined with the environment variable $CB_EXTRA_ARGS, so we can have this variable to set the default options (e.g. --symlink-install), and the extra feature to include other options as we please.
Problem: The cb command can be used with and without a workspace name as a first argument. If used without arguments, it will build the workspace that is currently activated. This requires to include aditional logic to detect if the first argument is the workspace name or a build option, in order to shift the arguments accordingly.
Possible solutions:
All colcon build options start with "--". This could be a way to detect if the first argument is meant to be a workspace name or an option.
Check if the first argument is in the list of workspaces. If not, use the active workspace and append the remainder arguments as build options. The problem here is if we want to use a workspace name but the name is wrong or it does not exist. Then it will be passed as an option without detecting the mistake.
Combine the previous two?
The text was updated successfully, but these errors were encountered:
Currently, the
cb
command allows passing custom options tocolcon build
through the environment variable$CB_EXTRA_ARGS
. It would be nice to be able to just append the desired build options directly after thecb
command.This can be done by shifting the workspace argument and passing the reminder
"$@"
to thecolcon build
command.This feature should also be combined with the environment variable
$CB_EXTRA_ARGS
, so we can have this variable to set the default options (e.g.--symlink-install
), and the extra feature to include other options as we please.Problem: The
cb
command can be used with and without a workspace name as a first argument. If used without arguments, it will build the workspace that is currently activated. This requires to include aditional logic to detect if the first argument is the workspace name or a build option, in order to shift the arguments accordingly.Possible solutions:
colcon build
options start with "--". This could be a way to detect if the first argument is meant to be a workspace name or an option.The text was updated successfully, but these errors were encountered: