Re: C-compilation with ASDF.

* Daniel Barlow <[email protected]>:

>> Also, I'm unclear on whether ASDF-files are meant to be edited by the
>> user or whether they're supposed to just work with no hassle.
>> (I.e. setting include-paths, library-paths, etc.)
> Really and ideally, the latter.

Ideally, though, people will have their libraries in a standard
location (as in, installed from some Debian-package or whatever), and
the C-compiler will have these standard locations in the defaults
include-paths/library-paths, so the reason for providing parameters
for this is just a convenience for people who want to build stuff
themselves and put it in weird locations.

The free BSDs put packages (ports/pkgsrc) in /usr/local or /usr/pkg,
though, so I don't know.  And like you say, it would be boring to
reimplement auto-tools in asdf, so I guess asdf shouldn't be littered
with all kinds of weird platform-conditionals.

> (defclass makefile-driven-source-file (source-file) ())

And autoconf-driven-source-file?

> (P.S. This sample code won't actually work as-is because of
> what-is-the-current-directory issues that I haven't thought about
> yet.

In case of a autoconf-driven setup, you could just configure with
--prefix=/my/lisp/binary/path and do make install, right?

autoconf is painful, by the way, are you sure you don't want it done
in Lisp instead? :)  Perhaps just a simple subset of autoconf.  Some
tools to do auto-tools-ish stuff.

-- 
Johannes Grødem <OpenPGP: 5055654C>




-------------------------------------------------------
This sf.net email is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en