[Octave-bug-tracker] [bug #39465] configure needs jvm.dll for Windows builds

[Philip Nienhuis]

Follow-up Comment #8, bug #39465 (project octave):

Yes; but ATM it is still a bit of a kludge here.
Anirudha has the superior option (although it looks like mine). We're all
awaiting merging of his tree into the formal mxe-octave tree.

As to my Java support cross-building on Linux:
- (Initially) I downloaded jni.h & jni_md.h from the links Michael supplied a
while ago into a mxe-octave/tools/java_include subdir
- (Later) I simply copied the <Windows JAVA_HOME>/include/win32 subdir
verbatim from the Windows 7 partition into <Linux JAVA_HOME>/include/ on that
same laptop)  (symlinking didn't work for unknown reason, I didn't bother to
investigate)
- and then added the relevant compile flags to the configure stanza in
mxe-octave/src/octave.mk (there's a catch in that this flag should point a
subdir higher up:)

--with-java-includedir=</full/path/to/JAVA_HOME> \

I also used to have jvm.dll copied (from that same Windows Java install) into
<Linux JAVA_HOME>/lib/i386/client/; later on I wiped it and just did:
"touch jvm.dll"
there - which proved sufficient as well.
Since Rik's patch for Octave configure.ac this isn't needed for Windows builds
anymore.

I set this up several months ago and never looked back; since then all my MXE
builds for Windows have Java working.

But again, I'd vote to have Anirudha's patches merged in a.s.a.p.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?39465>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/