Re: Actual libtool support routines
Adriaan de Groot <adridg-FlD2LfDziEhmR6Xm/[email protected]>
| Newsgroups | gmane.comp.tools.aap.devel |
|---|---|
| Message-ID | <[email protected]> |
On Thursday 28 August 2003 15:30, you wrote: > The simplest method would be to require something like ":import libtool". > We can make a collection of these optional modules. I'd go for that, with an :import command which would look for libtool.aap (just like default.aap) in some standard places. You can use :ltlib without any penalty without importing the module, it's just that AAP will complain that there is (say) no compile action defined for ltlibobjects when it comes time to build something. :import should work a lot like :include, but only search in system places. > Could this mechanism be automated? Thus as soon as something related to > Does this sound too complicated? It does; in particular since you'd have to recognize things like LIBADD (which might be a libtool thing) and every other subtlety of libtoolism. Perhaps using :ltlib should automatically load the libtool module, but in general I'd say that the penalty of having to do :import libtool in recipes for libtool is small; especially since other build weirdnesses might have a similar structure (:import distcc, anyone?), -- pub 1024D/FEA2A3FE 2002-06-18 Adriaan de Groot <[email protected]> Key fingerprint = 934E 31AA 80A7 723F 54F9 50ED 76AC EE01 FEA2 A3FE ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf