Re: JNI header files
Hi Mark, On Wednesday 16 July 2003 12:44, Mark Wielaard wrote: We don't seem to have real build support for creating JNI header files but instead have pre-generated .h files in our include file. Why is that? We do seem to detect which javah like program the user has installed. On my system it correctly detects gcjh. I would like them to be generated at build time so they won't get out of sync by accident. I assume gcjh is implemented in C? jamaicah is implemented in Java, so we have a bootstrap problem if we don't checkin the generated headers. We can solve this by checking in the JNI headers into our own repository only and remove it from the Classpath repository, but in case other VMs have similar problems, it might be better to check in the headers. Cheers, Andy. -- aicas GmbH /\ ASCII Ribbon Campaign Haid-und-Neu-Straße 18 * 76131 Karlsruhe \ / No HTML or RTF in mail http://www.aicas.com X No MS-Word in mail Tel: +49-721-663 968-24; Fax: +49-721-663 968-94 / \ Respect Open Standards ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: JNI header files
Mark Wielaard [EMAIL PROTECTED] writes: Hi, We don't seem to have real build support for creating JNI header files but instead have pre-generated .h files in our include file. Why is that? We do seem to detect which javah like program the user has installed. On my system it correctly detects gcjh. I would like them to be generated at build time so they won't get out of sync by accident. The native side wasn't changing much and keeping the header generation was more pain (to me) than just checking them in. I don't think it would be so bad if you added a target somewhere that regenerated them but wasn't part of the usual build. For distributions I wanted to distribute the headers as well. Brian -- Brian Jones [EMAIL PROTECTED] ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: JNI header files
Hi, On Wed, 2003-07-16 at 13:26, Andy Walter wrote: I assume gcjh is implemented in C? jamaicah is implemented in Java, so we have a bootstrap problem if we don't checkin the generated headers. We can solve this by checking in the JNI headers into our own repository only and remove it from the Classpath repository, but in case other VMs have similar problems, it might be better to check in the headers. Good point. kaffeh and gcjh are indeed both C implementations. Brian said it would be a good thing to supply header files with the distribution. But a build target to regenerate the files would be nice. Then it would be easy to check if the checked in files are still correct. Any takers to hack the make files? Cheers, Mark ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
