docs(nix/buildLisp): mention drawback of non-parallel compilation
To be fair this hardly matters since SBCL is quite fast, but compiling ironclad with ECL is quite the experience… Change-Id: Ib89cc50e5d557acec51fdb085bcbdfc99736221e Reviewed-on: https://cl.tvl.fyi/c/depot/+/3342 Tested-by: BuildkiteCI Reviewed-by: tazjin <mail@tazj.in>
This commit is contained in:
parent
47409b9610
commit
59195e76fa
1 changed files with 4 additions and 0 deletions
|
|
@ -18,6 +18,10 @@ restrictions should be highlighted:
|
||||||
|
|
||||||
* Only SBCL is supported (though the plan is to add support for at
|
* Only SBCL is supported (though the plan is to add support for at
|
||||||
least ABCL and Clozure CL, and maybe make it extensible)
|
least ABCL and Clozure CL, and maybe make it extensible)
|
||||||
|
* Parallel compilation is not possible: Since buildLisp doesn't encode
|
||||||
|
dependencies between components (i. e. source files) like ASDF,
|
||||||
|
it must compile source files in sequence to avoid errors due to
|
||||||
|
undefined symbols.
|
||||||
|
|
||||||
## Usage
|
## Usage
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue