This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: Question about clisp version naming
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin-apps at cygwin dot com
- Date: Sun, 15 Mar 2015 20:14:34 +0100
- Subject: Re: Question about clisp version naming
- Authentication-results: sourceware.org; auth=none
- References: <5500B536 dot 4050108 at cornell dot edu> <87bnju6wox dot fsf at Rainer dot invalid> <5505C36F dot 5030802 at cornell dot edu> <1426443595 dot 8104 dot 9 dot camel at cygwin dot com> <5505D57C dot 3040005 at cornell dot edu>
Ken Brown writes:
> I thought this would all work fine because lisp.dll was in the same
> directory as lisp.exe. And it does work fine for users of clisp. But
> I didn't think about applications like Maxima that would need to link
> against lisp.dll.
Maxima doesn't link against this library, it uses clisp' capability of
dumping an executable that has the application pre-loaded. In fact, if
you simply start the resulting EXE (not through the maxima wrapper)
you'll be greeted by a CLisp prompt.
> I think my new proposal (with /usr/bin/cyglisp.dll and
> /usr/lib/liblisp.dll.a) will work better. I don't know whether it's
> best to split off libclisp and clisp-devel subpackages. Fedora has a
> separate clisp-devel package, but it contains a lot of files that are
> currently (and have always been) in the main clisp package on
> Cygwin. At the moment, it's probably a higher priority to get
> something in the distro that Achim can use to build Maxima. But I'm
> open to suggestion on all of this.
I have a workaround for maxima and building and testing the package as
we speak. We can test the new clisp packaging more thoroughly later on.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada