Alright so I've got some very basic skeleton stuff put together using CMake and
SWIG. I followed the Python example and poked and prodded at it to make a Java
version of the same thing. Then added my stuff to it. So I've got:
FIND_PACKAGE(SWIG REQUIRED)
INCLUDE(${SWIG_USE_FILE})
FIND_PACKAGE
ms.com
>
>
>
> *From:* David Cole [mailto:david.c...@kitware.com]
> *Sent:* Thursday, March 18, 2010 4:16 PM
> *To:* Caron, Michael C. (US SSA)
> *Cc:* cmake@cmake.org
> *Subject:* Re: [CMake] CMake and SWIG
>
>
>
> If you open the file "C:/Program Files/CMake
...@kitware.com]
Sent: Thursday, March 18, 2010 4:16 PM
To: Caron, Michael C. (US SSA)
Cc: cmake@cmake.org
Subject: Re: [CMake] CMake and SWIG
If you open the file "C:/Program Files/CMake
2.8/share/cmake-2.8/Modules/FindSWIG.cmake" and read through it, you will see
exactly where CMake
If you open the file "C:/Program Files/CMake
2.8/share/cmake-2.8/Modules/FindSWIG.cmake" and read through it, you will
see exactly where CMake is looking for SWIG.
It uses:
FIND_PROGRAM(SWIG_EXECUTABLE swig)
(which means it's only looking in the PATH...)
So you can either:
set(SWIG_EXECUTABL
I'm just starting to try and get CMake and SWIG to play nice together. All
I've done is add:
FIND_PACKAGE(SWIG REQUIRED)
to an existing CMakeLists.txt file that has worked before now. With only this
addition I get:
CMake Error at C:/Program Files/CMake
2.8/share/cmake-2.8/Modules/FindSWIG.c
at cmake.org] On Behalf Of William
>A. Hoffman
>Sent: 24 February 2006 14:31
>To: Appru, Ian; brad.king at kitware.com
>Cc: cmake at cmake.org
>Subject: RE: [CMake] CMake and swig problem
>
>At 09:06 AM 2/24/2006, Ian.Appru at ubs.com wrote:
>>Thanks for your reply Brad,
>
Am Samstag 01 Dezember 2007 schrieb Hendrik Sattler:
> * The UseSWIG.cmake module:
> - uses it's first argument as target name for the module and thus also
> as output name, better:
> - combine target name with the current language and set OUTPUT_NAME
> property on target to the
Hi,
I trie to use cmake for an already existing project that currently uses
autotools.
There are several problems and some are related to bugs in module files or
missing module features. The bugs are reported here as they are easy to fix
and I don't want to do yet-another-registration:
* the
al Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of William
A. Hoffman
Sent: 24 February 2006 14:31
To: Appru, Ian; [EMAIL PROTECTED]
Cc: cmake@cmake.org
Subject: RE: [CMake] CMake and swig problem
At 09:06 AM 2/24/2006, [EMAIL PROTECTED] wrote:
>Thanks for yo
check your SWIG_ADD_MODULE
language variable against is 'csharp'
Cheers
Ian
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of William
A. Hoffman
Sent: 24 February 2006 14:03
To: Appru, Ian
Cc: cmake@cmake.org
Subject: RE: [CMake] CMake and swig probl
At 09:06 AM 2/24/2006, [EMAIL PROTECTED] wrote:
>Thanks for your reply Brad,
>
>I did (eventually) spot this line in the SWIG_ADD_MODULE macro.
>
>As I mentioned in conversation with Bill - think the thread accidentally
>went private there - I have decided to use my own UseSWIG-Java module
>and jus
m
specific requirement - java, python etc
Regards
Ian
-Original Message-
From: Brad King [mailto:[EMAIL PROTECTED]
Sent: 24 February 2006 13:39
To: Appru, Ian
Cc: [EMAIL PROTECTED]; cmake@cmake.org
Subject: Re: [CMake] CMake and swig problem
[EMAIL PROTECTED] wrote:
> I have retried
At 08:56 AM 2/24/2006, [EMAIL PROTECTED] wrote:
>The Java call System.loadLibrary() is platform dependant so should only
>need to
>use System.loadLibrary("MyJNI").
>
>It prepends 'lib' and uses .so suffix on unix and uses the .dll suffix
>on
>windows - no prefix.
>
>I am surprised that python wo
or now I will create my own local UseSWIG-Java module until
UseSWIG is
all things to all people.
Regards
Ian
-Original Message-
From: William A. Hoffman [mailto:[EMAIL PROTECTED]
Sent: 24 February 2006 13:03
To: Appru, Ian
Subject: RE: [CMake] CMake and swig problem
At 06:45 AM 2/24/20
[EMAIL PROTECTED] wrote:
I have retried my swig build with a version of cmake downloaded
yesterday
cmake --version
cmake version 2.3-20060222
Problem still exists - the solaris lib is generated as MyJNI.so rather
than libMyJNI.so.
If you're using SWIG_ADD_MODULE to create the library then t
ct: Re: [CMake] CMake and swig problem
At 09:45 AM 2/22/2006, [EMAIL PROTECTED] wrote:
>Content-class: urn:content-classes:message
>Content-Type: multipart/alternative;
>boundary="_=_NextPart_001_01C637BE.AF16F774"
>
>Hi,
>
>I am using the UseSWIG module on
Yes I am using a cvs version - couple weeks old.
It's a little tricky for me to get the cvs updates - but I will endeavor
to do so.
Cheers
Ian
>
>Hi,
>
>I am using the UseSWIG module on solaris to configure swig to generate
a
>java interface.
>However the C++ jni library generated has file name
At 09:45 AM 2/22/2006, [EMAIL PROTECTED] wrote:
>Content-class: urn:content-classes:message
>Content-Type: multipart/alternative;
>boundary="_=_NextPart_001_01C637BE.AF16F774"
>
>Hi,
>
>I am using the UseSWIG module on solaris to configure swig to generate a
>java interface.
>However th
Title: CMake and swig problem
Hi,
I am using the UseSWIG module on solaris to configure swig to generate a java interface.
However the C++ jni library generated has file name MyJNI.so rather than libMyJNI.so
On this limited info - any initial ideas on what might be the problem?
Regards
19 matches
Mail list logo