This is the mail archive of the
mailing list for the GCC project.
Re: Get rid of libtool? [was Re: Makefile problems]
- From: Jeff Sturm <jsturm at one-point dot com>
- To: Alexandre Oliva <aoliva at redhat dot com>
- Cc: Bryce McKinlay <bryce at waitaki dot otago dot ac dot nz>, Phil Edwards <phil at jaj dot com>, Nic Ferrier <nferrier at tapsellferrier dot co dot uk>, java at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- Date: Tue, 26 Feb 2002 20:44:11 -0500 (EST)
- Subject: Re: Get rid of libtool? [was Re: Makefile problems]
On 25 Feb 2002, Alexandre Oliva wrote:
> > - real incremental linking (*not* convenience libraries, which are a lousy
> > substitute).
> Which of the definitions of incremental linking are you talking about?
> > For instance, libgcj assumes public data symbols are exported by
> > default, which certainly isn't true on windows at least.
> Are you talking of -export-dynamic or something entirely different?
I'm talking about the dllimport/dllexport mess. Actually the dllexport is
solved, I think... it's the dllimport that can't be automated by libtool.
Point is, there are characteristics of shared lib implementations that
cannot be abstracted away... so is it worth trying?
The latter is a problem for libgcj on windows. C/C++ would use
__attribute__((dllimport)) to import data members. Java has no such