On 1/26/07, <b class="gmail_sendername">Mike Jackson</b> <<a href="mailto:mike.jackson@imts.us">mike.jackson@imts.us</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>OK.. dusting off the java cobb webs.... So JavaEmbedding is for<br>native Carbon/Cocoa (10.3.9/ppc) that need to instantiate a Java VM<br>_within_ the application itself... like a web browser would do if it<br>needed to display a Java Applet in a web page. This is NOT what VTK
<br>with java Wrappings are doing.<br><br> What the VTK/Java combo is doing is launching a native java<br>program. Then within that java program the VTK JNI libraries are used<br>to access VTK functionality. Do you understand the difference?
</blockquote><div><br>Yes I do... What I did *not* understand was the purpose of the JavaEmbedding framework, and CMake's old default choice of setting JAVA_AWT_LIBRARY to "-framework JavaEmbedding" ... (this was changed in CMake since the introduction of the intel macs to avoid trying to link a non-existent framework) -- silly me, I was thinking that was the way you linked in the AWT functionality... it did not occur to me that the functionality might exist in *both* JavaEmbedding and JavaVM until I read your email just now.
<br><br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">So I stand by my earlier, although cryptic post, and say that the<br>VTK java Wrappings need to link against
<br>"-framework JavaVM" instead of the JavaEmbedding Framework.</blockquote><div><br>Indeed. I changed my local build to use "-framework JavaVM" for JAVA_AWT_LIBRARY (and the corresponding header path for JAVA_AWT_INCLUDE_PATH) and it also works. Thanks for the clarifying email...
<br><br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">David, can you make the change please and lets see what the<br>dashboards come back with. Also is this a CMake change or a VTK Change?
</blockquote><div><br>Proper JAVA_AWT_* settings should eventually make their way into CMake's FindJNI.cmake module. For now, I'm considering ways to get them right by default ("out of the box") for Mac builds of VTK.
<br><br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Thanks to everyone for sticking with this problem.</blockquote><div><br>Yes, thank you all.
<br><br>Kenneth Sloan, if you're still reading this thread, try this on your Mac build of VTK:<br>- cd into your binary directory<br>- type "ccmake ." and hit return (or full path to ccmake if it's not in your env PATH)
<br>- type "t" to toggle to see advanced settings (t again to hide them)<br>- scroll down and set the following settings:<br>- JAVA_AWT_LIBRARY should be "-framework JavaVM"<br>- JAVA_AWT_INCLUDE_PATH should be something like "/System/Library/Frameworks/JavaVM.framework/Headers"
<br><br><br></div></div>Hope this finally helps / it sure did take more than a village,<br><br>:-)<br>David Cole<br>Kitware, Inc.<br><br>