[clbuild-devel] Optional parameter for 'clbuild {prebuild, lisp}'

[Albert Krewinkel]

Never mind.  For now, I created a new command `run-lisp' which takes an
optional parameter specifying the lisp-implementation to use.  All of
the following should work:

./clbuild run-lisp sbcl
./clbuild run-lisp clisp
./clbuild run-lisp $(which sbcl)

etc.

In the long run, I should try to implement an parameter
--implementation, which can be given to all commands.  This would
supersede my current ad-hoc solution.

Cheers,
Albert

Albert Krewinkel <krewinkel at gmx.net> writes:

> Hi,
>
> I compiled some changes which break backwards comparability, so I'd like
> to get feedback before actually committing it as a patch:
>
> Specifying the implementation to use by setting one of a couple of
> environment variables seems a bit clumsy to me.  It would be much nicer
> to specify the implementation from the command-line.
>
> As a first step towards that, I'd like a command like
> $ ./clbuild lisp ccl
>
> to have the intended effect.  However, this would break backwards
> comparability, as the current state forwards any additional command line
> token directly to the implementation.
>
> A patch implementing this (and which has an incredibly bad name) was
> pushed into an experimental repo here:
>
> http://darcs.moltkeplatz.de/clbuild
>
> The patch also contains rudimentary support for ECL.
>
> Comments welcome
>
> Cheers,
> Albert
> _______________________________________________
> clbuild-devel mailing list
> clbuild-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/clbuild-devel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 193 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/clbuild-devel/attachments/20081128/a5741617/attachment.sig>