Re: Re: C-compilation with ASDF.
Daniel Barlow <[email protected]>
| Newsgroups | gmane.lisp.cclan.general |
|---|---|
| Message-ID | <[email protected]> |
"Johannes Grødem" <[email protected]> writes: > 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. Tried building a Gnome application recently? There are hordes of little helper programs that you're supposed to somehow use to make sure you get the include paths corresponding to the version you're running gnome-autogen.sh gtk-config --cflags glib-config --cflags gnome-config --cflags .... >> (defclass makefile-driven-source-file (source-file) ()) > > And autoconf-driven-source-file? I hope not. Um. But perhaps we need some way to tell asdf how to generate the Makefile > 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. I don't actually _want_ to make anyone use autoconf for anything. If starting from scratch, there may well be easier ways (perhaps people want to look at Marco's CL-CONFIGURATION for this?). But if we're talking about using libraries that are already out there, then certainly in the unix world there's enough systems that come with bits of autoconf-plugin m4 macros that we may as well let users take advantage(sic) of them, if the users feel it would make their lives easier. I'm aware that my take on this is very unix-centric. Unix is what I use. What do Windows/Mac/other platform users need when they're compiling foreign code? -dan -- http://ww.telent.net/cliki/ - Link farm for free CL-on-Unix resources ------------------------------------------------------- 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