build-all

[kchanqvq]

I really wish we keep the old way of building everything (or sufficiently large number of things) from a single Lisp process,

Also currently there's asymmetry between Node and other REPLs. Others have build.lisp, but Node doesn't have build.lisp and has the build function directly in jscl.lisp. I wish these can be symmetric, so that Node isn't special (say someone want to build Deno/Web/future-other-platform REPL without using Node).

[kchanqvq]

How about let's put all the build functions in jscl.lisp? Then to compile from compiled JSCL, do something like node jscl-node.js --eval "(jscl:build-deno-repl)". And in make.sh/build-all we can just compile every REPL, not relying on node. bootstrap.sh can pick a starting REPL and exercise bootstrap.

[davazp]

Yeah I know it's a bit inconvenient now.

I want to try to make jscl-node also built with compile-application too. But it was a bit trickier because without it there is no meaningful FS support. I'll try at some point. We can build jscl.js and use a small JS script to load jscl.js and use it to build node REPL. But it's trickier so I left it for now.

I prefer bootstrap to be about the most minimal core possible. Just jscl.js that is a JS module with the most common thing between all runtimes.

Everything else be something that the user could built on top without having to bootstrap jscl itself.

At some point it'd nice to have more build from Lisp, but for now as it involves multiple processes it's easier from make.sh.

How about let's put all the build functions in jscl.lisp? Then to compile from compiled JSCL, do something like node jscl-node.js --eval "(jscl:build-deno-repl)". And in make.sh/build-all we can just compile every REPL, not relying on node. bootstrap.sh can pick a starting REPL and exercise bootstrap.

Well that's very similar to what we have, but now we have one extra file to load, jscl.lisp and then the build.lisp, right? I like the colocated build.lisp with the platforms and copying files.

Maybe for now you can define a user local build.lisp that does load all systems and build-all on top of all of them?

[kchanqvq]

I like the colocated build.lisp with the platforms and copying files.

Should this also be applied to Node REPL? i.e. have a build.lisp under node/ and load it when necessary.

[davazp]

We can add the build.lisp even if even the node repl build is different from the others now.
It's still quite similar. The biggest annoying difference is that the node repl has to use the jscl-xc package, rather than the build.

[kchanqvq]

The biggest annoying difference is that the node repl has to use the jscl-xc package, rather than the build.

I see. So currently if it is cross-compiled from SBCL, it need to use jscl-xc; if it's compiled from JSCL, it can just use jscl? I wonder if this difference can be resolved.

[davazp]

Exactly. Some differences can be minimized by using :use. Because it's a single statement that is easy to add a conditional reader.

But the REPLs are using some internal features that we do not want to export from the package yet I'd say.

We could create another package jscl/impl where we export a bunch of stuff for internal use but consider the package internal? Maybe all of jscl can be exported in jscl/impl.

It's a bit hacky still 🤔 not sure if I like it.