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

Support for automatic configuration within cargo.toml #1

Open
MarcosCosmos opened this issue Jun 4, 2018 · 1 comment
Open

Support for automatic configuration within cargo.toml #1

MarcosCosmos opened this issue Jun 4, 2018 · 1 comment

Comments

@MarcosCosmos
Copy link

MarcosCosmos commented Jun 4, 2018

I'm not sure if it's actually possible, but I think it'd be conveniant to specify the destination file via cargo.toml (with the src being implicitly lib.rs or main.rs already, although it could also be configured). Additionally (if possible), it'd be nice to have some kind of implicit build.rs ship with the bundler crate. (That is, rather than having to manually write or copy one into your project).

It was always one of the key motivations for me of porting my project to rust.

Do you know if it's possible? If you haven't already looked into it, I might fork your project and give it a go over the weekend.

@MarcosCosmos MarcosCosmos changed the title Support for configuration within cargo.toml Support for automatic configuration within cargo.toml Jun 4, 2018
@slava-sh
Copy link
Owner

It's true that the inputs and outputs could be configurable. I used the bundler executable as part of a bash pipeline and just didn't need more flexibility.

I don't think it's possible to have a completely implicit build.rs script. A reasonable solution might be providing a concise and ready-to-use build.rs in the documentation. I'm happy to accept a PR if you'd like to work on it.

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