Re: The autoconf macros business.
- From: Drazen Kacar <dave srce hr>
- To: Tim Janik <timj gtk org>
- Cc: Miguel de Icaza <miguel nuclecu unam mx>, Owen Taylor <otaylor gtk org>, gnome-hackers nuclecu unam mx, gnome-devel-list gnome org
- Subject: Re: The autoconf macros business.
- Date: Sat, 10 Apr 1999 01:40:48 +0200
Tim Janik wrote:
> also, the --libs-only-L and --libs-only-l options featured by gnome-config
> should probably also be featured by gtk-config and glib-config and even
> be furtherly split up into --libs-only-L, --libs-only-l, --libs-only-l-self
> and --libs-only-l-system (where --libs-only-l is a superset of
> --libs-only-l-self (e.g. -lglib -lgmodule -lgthread) and
> --libs-only-l-system (e.g. -lpthread -ldl -lm) so we can implement
> proper implementation-level-ordered chaining of the *-config scripts.
What is the intended behaviour with -R flag if I ask for --libs-only-L?
I've changed all *-config scripts, so they now output -L/usr/local/lib
and -R/usr/local/lib on my systems. If I ask for --libs-only-L, I
currently get both of them, which is fine with me, but I'm not sure
that someone who uses that in his config script or Makefile would agree
with me.
There is no --libs-only-R or --libs-only-L-and-R, so I'm somewhat clueless.
--
.-. .-. Life is a sexually transmitted disease.
(_ \ / _)
| dave@srce.hr
| dave@fly.cc.fer.hr
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]