This is the mail archive of the
java-discuss@sourceware.cygnus.com
mailing list for the Java project.
RE: Proposal for CNI/JNI problems
- To: classpath at gnu dot org, "'Aaron M. Renn'" <arenn at urbanophile dot com>, Paul Fisher <pnfisher at redhat dot com>
- Subject: RE: Proposal for CNI/JNI problems
- From: "Lam.Mark" <LamM at intgame dot com>
- Date: Thu, 13 Jan 2000 10:01:52 -0800
- Cc: java-discuss at sourceware dot cygnus dot com
>I think this should be considered very carefully. I would like to avoid
>these dependencies if possible. Particularly any dependencies on gcc.
>Personally, it looks like in the core classes there will be so little
>code that the JNI/CNI thing could be handled with #ifdef CNI/JNI and
>a configure time option added to enable it. Or a set of macros might
>handled almost everything reasonably well.
Pardon me, but isn't depending on a configure time option simply shifting
the dependency from gcc to the configurer? I work on Win32 systems, and in
my case, a C++ compiler is readily available but I have difficulty finding a
configurer. I may be missing the point, but could someone in the know
please clarify this? Thanks.