This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: [libava/win32]: Don't add dll[im/ex]port attributes to libgcj,unless dll build
- From: Jeff Sturm <jsturm at one-point dot com>
- To: Mohan Embar <gnustuff at thisiscool dot com>
- Cc: Danny Smith <danny_r_smith_2001 at yahoo dot co dot nz>, Bryce McKinlay <bryce at mckinlay dot net dot nz>, <java-patches at gcc dot gnu dot org>
- Date: Thu, 7 Aug 2003 12:42:02 -0400 (EDT)
- Subject: Re: [libava/win32]: Don't add dll[im/ex]port attributes to libgcj,unless dll build
On Thu, 7 Aug 2003, Mohan Embar wrote:
> >>> I actually prefer the .def file option discussed here:
> >>> http://gcc.gnu.org/ml/java/2003-08/msg00076.html
>
> To my naive eyes, requiring a separate .DEF file for such matters
> would create a dual-maintenance issue. I realize that the number
> of exported functions is relatively static, but I don't see harm in such
> macros, even if a different macro is needed for CNI-related exports
> vs. JNI-related exports.
I suppose a .def file is the analog of ELF version scripts. Libgcj
will likely have the latter anyway sometime after binary compatibility is
done.
Jeff