On Wed, Jan 10, 2001 at 09:22:30PM -0800, [EMAIL PROTECTED] wrote: > > > It works for me. > > > > I only have two mild concerns: > > > > 1) APR's use of .la files when the user doesn't use libtool (noted above) > > 2) APRVARS.in using variables not in the APR namespace. See apr-util's > > export_vars.sh.in for what I think is the Right Way (and how it is used > > in Apache's configure.in). By using unprotected names in APRVARS, we > > might "stomp" on the user's vars. > > > > I've got no immediate answer for (1), and (2) is just something that has > > been in mind for a while. I'll get around to it at some point, probably > > after JimJag's flag revision stuff. > > Can I suggest a possible solution for 1, and agree 100% with 2? The > possible solution, is to use two variables, LIBTOOL_LIBS, and > NON_LIBTOOL_LIBS. These names are probably wrong, call they what you want > to. > > The idea is that if you use LIBTOOL, you have to add the libraries in > LIBTOOL_LIBS, if not you have to use NON_LIBTOOL_LIBS. If you don't use > libtool, you basically have to add the NON_LIBTOOL_LIBS to APR_LIBS. > > Does that make sense?
Somewhat... but it does mean that we'd be looking down into .libs for the libraries to put into NON_LIBTOOL_LIBS. Not sure what I think about that one... (reaching into .libs is the basic question: do we or don't we?) Sascha may have an idea here. Cheers, -g -- Greg Stein, http://www.lyra.org/