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: Mohan Embar <gnustuff at thisiscool dot com>
- To: Danny Smith <danny_r_smith_2001 at yahoo dot co dot nz>, Bryce McKinlay <bryce at mckinlay dot net dot nz>
- Cc: java-patches at gcc dot gnu dot org
- Date: Thu, 07 Aug 2003 09:23:17 -0500
- Subject: Re: [libava/win32]: Don't add dll[im/ex]port attributes to libgcj, unless dll build
- Reply-to: gnustuff at thisiscool dot com
Hi People,
>>> 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.
The only other disadvantage I can see is that they would be confusing
for non-Windows folks.
I'd appreciate any education / enligtenment on this issue.
-- Mohan
http://www.thisiscool.com/
http://www.animalsong.org/