Fare,

(CC'ing the clasp-devel list, also)

i would like to ask your bird's eye view perspective on this:

what do you think would be a reasonable/practical/feasible build system for clasp if its build were rewritten today?

currently it's using waf, a python thingy which works nicely at the initial phase, when things are simple, but it is a major PITA after that.

now that there's quicklisp to fetch the dependencies, would it make sense to just write a Common Lisp program as the build script? there's already a python.exe and a waf dependency... a working cl.exe as a dependency is not any worse than that i guess.

or do you have any better ideas than a CL program, that is simple but extensible for complex tasks? (e.g. compiling custom programs that scrape through the sources, generating intermediate build artifacts, whole program compilation with extensions on the C++ level (clasp is LLVM and C++))

feel free to be short, and thanks for your time!

- attila PGP: 5D5F 45C7 DFCD 0A39