>>>>> "James" == James Amundson <amundson@fnal.gov> writes:
James> Yes. I'll check for mk:defsystem, etc. I'm only using two
James> files from CLOCC, defsystem.lisp and run-lisp, so it might
James> be a good idea to bundle a default version with the maxima
James> distribution. Then again, it might not. I haven't
James> decided. At the very least, I would seek the blessing of
James> the CLOCC maintainers before doing so. I would also provide
James> the option to use an external version of those files.
matlisp bundles a copy of CLOCC defsystem. Since mk:defsystem and
maxima are "free", it shouldn't be a problem. You just have to
remember to keep it up-to-date.
>> Say, for example, I wanted to compile maxima against GCL, CMUCL, and
>> Clisp, 'cause I'm a geek and want to use different lisps for different
>> types of jobs:
>>
>> ./configure --use-gcl --use-cmucl --use-clisp --default clisp
James> ...
>> Sorry if I'm off base again, but it sort of seemed like a cool idea.
James> I think it's a cool idea, too. I had planned to do almost exactly what
James> you are suggesting.
Isn't this normally done as follows:
mkdir maxima-on-gcl
cd maxima-on-gcl
../configure --use-gcl
...
cd ..
mkdir maxima-on-cmucl
cd maxima-on-cmucl
../configure --use-cmucl
...
James> I'm happy to do the auto(conf,make) work. It's well within
James> my expertise. I can't promise to finish it for at least a
James> month, however. (In Real Life I'm in the process of
You could start with the autoconf file from matlisp as a start. It
only supports ACL and CMUCL, but it works. It also uses logical
pathnames to name everything and automatically figures out how to set
up the translations.
Ray