Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing option to specify log path #555

Closed
bi3ri opened this issue May 4, 2023 · 2 comments
Closed

Missing option to specify log path #555

bi3ri opened this issue May 4, 2023 · 2 comments

Comments

@bi3ri
Copy link

bi3ri commented May 4, 2023

Hello!

there are several options to specify base, install, and build path, but for logs it is missing.

colcon build \
      --base-paths ereal_ws/src \
      --install-base ereal_ws/install \
      --build-base ereal_ws/build \
      --log-base ereal_ws/log \

It seems there was a plan to add this feature though, because the command above results in the following output.

usage: colcon [-h] [--log-base LOG_BASE] [--log-level LOG_LEVEL] {build,clean,extension-points,extensions,graph,info,list,metadata,mixin,test,test-result,version-check} ...
colcon: error: unrecognized arguments: --log-base ...

Thanks!
Johannes

@cottsay
Copy link
Member

cottsay commented May 4, 2023

Hi, because the log --log-base option affects colcon before it even parses the verb, that particular option needs to be passed before the verb, as it is shown in the example you posted.
This should work how you expect:

colcon --log-base ereal_ws/log build \
      --base-paths ereal_ws/src \
      --install-base ereal_ws/install \
      --build-base ereal_ws/build \

@bi3ri
Copy link
Author

bi3ri commented May 5, 2023

Thanks @cottsay!

  --log-base LOG_BASE   The base path for all log directories (default: ./log, to
                        disable: /dev/null)

That option specifies the default log path though. I was searching for an option to define the log path for each build separately.

Okay, I did misunderstand the documentation. The log path is specified for each build separately.

@bi3ri bi3ri closed this as completed May 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants