Re: Additional link flags for HP aCC and SGI CC

[Ludovic Courtès]

Hi Gary,

Today, 2 hours, 29 minutes, 36 seconds ago, Gary V. Vaughan wrote:
> It does, but the interface to the user doesn't change depending on the
> host machine.  -Xcompiler and -Xlinker are there so that if we find a
> missing abstraction, libtool users can continue to work while we figure
> out how to incorporate a clean abstraction into the user interface.

I see.

> Libtool is designed to work without automake and autoconf too.  So,
> although your solution works well for you, it will be of benefit to the
> most people if we can move it into libtool itself along with all the
> other compiler specific knowledge that is stored there.
> 
> You are right that there are a plethora of compilation options, and
> we strive to boil those down to a uniform interface, so that libtool
> users don't need to learn them... they should be able to tell libtool
> what they want to do, and *it* figures out which options to pass to
> the compiler and linker.  Of course, we only have the commonly used
> compilation features abstracted away at the moment, and there will always
> be room to move features up from the compiler driver level to the
> libtool interface...

Ok.  I didn't know moving such higher-level features into Libtool was
planned since there are currently mostly generic features.  I also
thought this would go way beyond the goal of a "generic library support
script".

Libtool options like `--cxx-flags=std,local-template', `--multi-thread',
`--abi=32' (although this one is very platform specific anyway since
`--abi=mips2' wouldn't make much sense on IA32), or even things like
`--warnings=2', `--optimization=3' and so on would be very cool.  For
common options, another solution would be to let the user use GCC-like
switches (eg. `-O2', `-Wall') which would then be converted into the
target compiler switches.  What do you think?

Thanks!
Ludovic.