libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: flat namespaces redux


From: Yves de Champlain
Subject: Re: flat namespaces redux
Date: Tue, 04 Feb 2003 20:16:10 -0500

From my point of view, portable software just means
that it should work well in regards to platform-specific
features (or bugs).

yves

Le Mardi, 4 févr 2003, à 00:59 Canada/Eastern, Robert Boehne a écrit :

Hello,

Maybe I don't understand OS X, but as I see it, any library
that needs a two level namespace would not build on any other OS
because OS X is the only OS that supports this feature.
Now, if that is the case, it doesn't make any sense for Libtool
(a tool for portable library creation & use) to support a feature
that is only present on a single platform.  Does that make sense?

Robert Boehne

Peter O'Gorman wrote:

On Tuesday, February 4, 2003, at 12:01  AM, Benjamin Reed wrote:

cc -multiply_defined suppress -prebind blah || cc -flat_namespace
-undefined suppress blah

1. libkdeui's LIBADD is "-lkdecore"
2. the first half of the link complains that -lqt-mt is indirectly
referenced
3. it builds the library flat, and continues on

when what *should* happen is it dies at #2, and we add -lqt-mt to
libkdeui's LIBADD like it should be.

Why? An option to stop if two_level namespace can't be built, I can see
as a good thing for people porting stuff to darwin, however some stuff
is quite happy being flat, even if it only missing the usual environ
symbol, and imo, libtool shouldn't die by default.

The default should be to continue if possible unless told otherwise,
the fewer people who have to add custom flags and options the better.

Peter

_______________________________________________
Libtool mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/libtool


_______________________________________________
Libtool mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/libtool






reply via email to

[Prev in Thread] Current Thread [Next in Thread]