Jared Forsyth
Jared Forsyth
yeah for bucklescript I guess it's not a single target. So yeah that's totally fine. The "target" key would just be a directory in that case I guess
hmm I think that makes in more confusing. I think splitting it up by "input -> output" makes more sense than splitting it up by engine
for example, how do I specify that I want BS to compile two things separately to different destination directories?
sure. and if you want different flags for the different targets? it just seems like unifying around the concept of a build target will make the configuration more natural --...
@vramana that array configuration looks good to me. Can jenga just kick off 2 separate build processes? Or maybe our `rebel` cli would do that instead, parsing the json w/...
``` mkdir -p something/src cd something echo "{}" > package.json echo 'print_endline "hello";' > src/hello.re rebel -P # in a diff tab ./_build/src/app.out # `hello` echo 'print_endline "hello all";' >...
``` 13:23:34 rsn/something 0 $ rebel -P *** jenga: [79301] root=/Users/jared/clone/rsn/something, sys=Darwin, j=1, f=1 (NO_VERSION_UTIL) *** jenga: 6/6 targets are up to date *** jenga: done (#1, 107ms, heap=7.35156m, stat=20,...
except for running GC for some reason ??
boo :/ who cares if its fast if it doesn't work
right watchman has caused me so much grief