On Mon, 2008-06-16 at 10:02 +0200, Alexander Neundorf wrote:
[...]
> Seriously, why is a wrapper for the compiler/linker required AT ALL if the
> calls to these tools are made from _generated_ files ?
AFAIU the motivation of libtool to provide OS-independent (and toolchain
independent?) means to compile and link (etc.).
> The generated files should just contain the appropriate calls for the
> respective commands.
But these calls are - e.g. for shared libraries - not identical. The Gnu
toolchain is not everything.
> This layer of abstraction is unnecessary and IMO just adds confusion.
> (modifying libtool so that it calls unitool even seems to add yet another
> layer which can potentially break or bitrot etc.)
I know of more than one "occasion" where "gcc" et.al. actually where
wrappers around the actually binaries to check and guarantee commandline
parameters and options (some must be there, some mustn't be there, ...).
Usually sane Makefiles (and sane autotools usages) are enough for that.
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
--
To unsubscribe from this list: send the line "unsubscribe linux-embedded" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
