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

auto-detect --merge-install #102

Closed
NikolasE opened this issue Apr 23, 2020 · 2 comments
Closed

auto-detect --merge-install #102

NikolasE opened this issue Apr 23, 2020 · 2 comments
Labels
question Further information is requested

Comments

@NikolasE
Copy link

Why is colcon not starting the build process if I omit the '--merge-install' flag after the first run? Can't we assume that the user intends to build in the same layout like last time?
So instead of forcing the user to type --merge-install every time (or use an alias or similar), couldn't colcon use the detected layout?

@dirk-thomas dirk-thomas added the question Further information is requested label Apr 23, 2020
@dirk-thomas
Copy link
Member

Can't we assume that the user intends to build in the same layout like last time?

I am not sure that would be a good heuristic. What if the user intended to do an isolated build and forgot that the workspace was previously built merged? If this choice would happen automatically there is no easy way to choose the opposite.

I think the concept of profiles as described in colcon/colcon-core#168 would be a better solution for this use case. The arguments from a previous invocation would be persistent and reapplied in future invocations.

@NikolasE
Copy link
Author

Yes, that sounds like a good way to achieve what I was thinking about!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Development

No branches or pull requests

2 participants