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

Allow the user to define a specific bin output directory #17

Closed
Telokis opened this issue Jan 5, 2020 · 4 comments
Closed

Allow the user to define a specific bin output directory #17

Telokis opened this issue Jan 5, 2020 · 4 comments

Comments

@Telokis
Copy link
Contributor

Telokis commented Jan 5, 2020

The current behavior of sw is to output bin files to .sw/out/<hash>/.
This is not ideal because the user doesn't know the value of <hash>. We have to look at the build output to see where the file was outputted.

My suggestion is to add a CLI option like --out-dir which could be set to any directory (existing or not). sw would then output everything there.
This could also be specified inside the sw.cpp, allowing for consistent setup without relying on the user to remember to use the CLI option.

We could also have both a CLI option and a sw.cpp config but the CLI option takes precedence, for example.

@egorpugin
Copy link
Contributor

Added sw build --output-dir bin.
Update sw and try it!

@Telokis
Copy link
Contributor Author

Telokis commented Jan 5, 2020

Works perfectly, thank you!

@Telokis
Copy link
Contributor Author

Telokis commented Jan 6, 2020

Are you considering the other part of the issue?

This could also be specified inside the sw.cpp, allowing for consistent setup without relying on the user to remember to use the CLI option.

We could also have both a CLI option and a sw.cpp config but the CLI option takes precedence, for example.

@egorpugin
Copy link
Contributor

egorpugin commented Jan 6, 2020

Such thing was earlier (also in cppan). It is disabled at the moment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants