Add a one-step build script.
Closed this issue · 5 comments
It would be lovely if we could put together something like a Makefile so that there was a single command that would ensure that dependencies (like wattsi) were downloaded/updated/built, and would execute the various build commands to produce the generated documents.
That would be nice, yeah, I failed to even build freepascal :)
I think we have this now from the changes in #13. If you run the build.sh from that branch, it does everything for you—including the fact that with #10 landed, the build no longer requires you to have wattsi installed locally; if you don’t, in runs it on the server side and sends the results down, and the rest of the build just uses that output (instead of trying to generate it with wattsi locally).
#13 did a lot, but I interpret this as also doing a git checkout of https://github.com/whatwg/html.
Probably best to do after #15. With that design in place this becomes basically "if the source directory doesn't exist, git clone into it."
Then we can tell people "to get started building HTML, git clone html-build and run html-build/build.sh. If all goes well, you should have output in html-output/, and you can edit html/ and run html-build/build.sh from there."
Hmm, or maybe that would end up confusing since it would set origin to whatwg/html instead of yourfork/html :(. We could make it prompt for the git remote you want to use I guess, with default whatwg/html?
#13 did a lot, but I interpret this as also doing a git checkout of https://github.com/whatwg/html.
Ah, true. I had been assuming that other users would all just already have the html repo checked out, as I do. But if they haven’t yet, the build rightly should just get it for them and keep on going.
Probably best to do after #15. With that design in place this becomes basically "if the source directory doesn't exist, git clone into it."
Yeah, agreed.
We could make it prompt for the git remote you want to use I guess, with default whatwg/html?
That would make sense, yeah.