On Fri, 26 May 2000, Michael Matz wrote:
> On Thu, 25 May 2000, Kevin Atkinson wrote:
> >
> > Maybe I am missing something here but can't you just let g++ handle all
> > the C++ issues. If G++ does call the native linker and you need to pass
> > special options too it this native linker is bound to be the same as the
> > linker used for C programs. So then can't C++ libtool get the necessarily
> > options to pass (like the rpath stuff) from the C part of libtool. Or am
> > I missing something?
>
> Basically it would be not that bad for the C++ part to use as default the
> C options having to do with linker work. But that needs some fiddling,
> e.g. on C++ the compiler needs to link libraries, not ld itself. On
> some platforms this is also the case for C right now, but on others ld
> is used directly.
>
> And also right now the two language configurations are splitted, so we
> have no access to ltcf-c.sh from ltcf-cxx.sh (besides from duplicating
> code ;) ) Also the actual arguments depend on the compiler used, so e.g.
> if the user had used native cc for C and GNU g++ for C++ we would loose
> (though there is some abstraction mechanism like ${Wl})
Wouldn't that not depend on the user but what information is in
ltcf-cxx.sh. I image for most platforms gcc is a supported compiler as
well as the native cc.
> Hmm, unless I miss something and we invest some work for infrastructure,
> the easiest way IMHO is a thoughtful cut and paste from ltcf-c.sh, (which
> basically is your idea, only with more hand work ;)
Well if I could help out in this let me know.
> May be later it would really be a good idea to not only parameterize the
> configuration on the language, but also on the linker (well we only have
> GNU or native), to not duplicate all the linker dependent work in the
> other language modules (if there are ever more than two ;)
Yes this would be a good idea. Especially when you start adding support
for Java, Ada, and the link....
Well if you need someone to do testing and fiddling I would defiantly be
willing to help. Some basic guidance as what needs fiddling is all I
would require.
Another thing I really need is support for dropping static library from
the link list when creating shared libraries.
Hopefully since KDE will be using it some KDE people will help to improve
the C++ support. I am sure they will run into the problem with non-pic
static libraries being linked into shared libraries also. Especially on
Solaries.
--
Kevin Atkinson
[EMAIL PROTECTED]
http://metalab.unc.edu/kevina/
