-
Notifications
You must be signed in to change notification settings - Fork 177
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
Provide a single build system #203
Comments
What would the benefits be? |
The docs could be more concise. Instead of "If you use AS, use npm. If you use C/C++, D, Go, Odin use make. If you use ..." we could simple say "run Windows doesn't provide Make out of the box. A Using |
Wouldn't we still need to rely on the source language's build system? Eg: cargo for Rust, node/npm for Assemblyscript, nimble for Nim, etc. I'd rather have users use their language's existing build system rather than trying to force our own. I guess what we could do is have Bundling |
What I mean is more like "Copy the contents of the Makefile to the CLI." |
For languages like Go where the Makefile is just wrapping a single command that maybe makes sense, but for C/C++ we actually use the dependency tracking features of Make and reimplementing that ourselves would be way too much work. |
Okay, let's do it the other way around: Provide a Makefile for all languages. But languages like Rust still get the mention of the "usual" way. This should make the CLI easier to maintain, since we don't have to include several commands to build the cart. |
Currently we have several different ways to compile the cart.wasm.
At the same time, we have
w4 watch
that uses language specific build commands.I suggest we add something like
w4 build
. This could build the different languages.Also it might be a good idea to not use makefiles.
Those are less common on Windows than on *nix Systems.
The text was updated successfully, but these errors were encountered: