sbcl.sbcl/src/assembly/master.lisp
Douglas Katzman 0abf67fd58 Relax requirement on current directory during build
After this it is more-or-less possible to have the SBCL root directory
be a subdirectory of the current dir. Everything in src/cold finds required
files as siblings, so if SBCL is in "mumble/something/sbcl", you needn't
change dir into "sbcl" but instead, while in "mumble" it works to load
"something/sbcl/src/cold/shared"

A quick not-too-exciting example:
* (setq *sbcl-local-target-features-file* "sbcl/local-target-features.lisp-expr")
"sbcl/local-target-features.lisp-expr"
* (load "sbcl/src/cold/shared")
T

In real-world usage, the SBCL directory would be buried deeper in the tree
and you don't want to physically change dir into it because reasons.

It should be easier to parallelize crossbuild-runner too. With suitable
input and output directories, each architecture can place its artifacts into
a different fasl tree while pulling sources from the common location.
2021-06-30 11:25:13 -04:00

8 lines
346 B
Common Lisp

;; If you change this, note that 'slam.lisp' has to be able to parse this form
(mapc (lambda (x) (load (sb-cold:stem-source-path x) :verbose nil :print nil))
'("src/assembly/{arch}/tramps"
"src/assembly/{arch}/assem-rtns"
"src/assembly/{arch}/array"
"src/assembly/{arch}/arith"
"src/assembly/{arch}/alloc"))