I could be wrong... I'm not a huge mingw user, but I think this is the
expected library naming for a mingw build.
If so, then the VTK java wrapping code is just not going to work on mingw as
it stands now. I suspect there are few, if any, users of java wrappers using
a mingw build of VTK. If
David,
IMHOP, the naming of the java DLL is dictated by the java behavior on
the platform, not the compiler in use. Static libraries can be named
with the lib prefix according to the compiler requirements, but runtime
libraries (on windows DLLs) need to be named according to the runtime
users
What is the primary user of a mingw compiler system trying to achieve?
Somebody trying to build unix-y stuff for Windows?
Or somebody trying to build unix-y stuff to still be unix-y in an MSYS shell
environment?
Because the answer is ambiguous, there is no right answer. Therefore, we've
chosen
Start here:
http://cmake.org/cmake/help/cmake-2-8-docs.html#variable:CMAKE_SHARED_LIBRARY_PREFIX
On Fri, Jul 30, 2010 at 1:54 PM, Jim Peterson ji...@cox.net wrote:
David,
IMHOP, the naming of the java DLL is dictated by the java behavior on the
platform, not the compiler in use. Static
you can do...
SET_TARGET_PROPERTIES( target name PROPERTIES
PREFIX
SUFFIX
)
well probably the suffix you want to leave as .dll... just copied from
something that makes the library exactly what the target name is.
On Fri, Jul 30, 2010 at 10:54 AM, Jim
