|
From: | Kon Lovett |
Subject: | Re: [Chicken-users] .meta needs on a per platform basis |
Date: | Mon, 8 Jan 2007 08:21:30 -0800 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jan 8, 2007, at 4:43 AM, felix winkelmann wrote:
On 1/7/07, Kon Lovett <address@hidden> wrote:Hi, Got a problem w/ the .meta file needs entry. I think some logic there to state the platform would be useful. Ex: z3, pty, & rlimit cannot compile w/ Windows (assuming no Interex/Cygwin), but an egg that "needs" one or more of these for unix could still work w/ windows - just w/ reduced features. Am I missing something?Would an extension of the needs clause like this be sufficient: needs = (needs EXTENSION-ID ...) | (needs ((FEATURE-ID EXTENSION-ID ...) ...) i.e. like the body of a `cond-expand' form?
I think so. I use forms like this in my code (.scm & .setup): #+unix ... #+windows ...& it works fine for me. The only problem being the different .egg rqrmnts for platforms. (Another possibility is a "tool" that writes stubs for all exported variables so every egg is "available" on every platform.)
Thank you, Kon
cheers, felix
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iEYEARECAAYFAkWib4sACgkQJJNoeGe+5O4k/wCdGW/5rTEO/I5o69zbpPFeFAJ5 928An3iTwKwALsgsNWb+OfWfrHmmDA/N =vr5x -----END PGP SIGNATURE-----
[Prev in Thread] | Current Thread | [Next in Thread] |