Hallo everybody.
May I ask you for a help with SWIG module in CMake? I need to create more
wrapping libraries from one set of .i SWIG files. To use SWIG from CMake is
really trivial for one wrapped language, but I need to create more wrappers
in one step, as illustrated below:
I have directory
Daniel,
I figured out a solution which is more a trick than anything else. Basically,
I created an empty .i file as a stub for each language. For example, you have
Module.i and you could add ModulePython.i which contains:
%include Module.i. I then use CMake with these stubs.
This works but
Great, this is a good idea, thank you very much!
I have tried to create wrap/python/ModulePy.i including the original
wrap/Module.i only, and when it was called as
.../python $ swig -c++ -python -I../ Module.py
everything seemed to be OK (well, I did not try to compile it, I just
I am sorry - the previous mail was wrong. The directives:
SET_SOURCE_FILES_PROPERTIES( ErisPython.i PROPERTIES CPLUSPLUS
ON )
SET_SOURCE_FILES_PROPERTIES( ErisPython.i PROPERTIES SWIG_FLAGS -I../)
seems to work fine. The -I../ flag is set in the SWIG call. I had to miss
At 09:49 PM 7/22/2006, William A. Hoffman wrote:
At 06:09 PM 7/22/2006, William A. Hoffman wrote:
OK, found the problem. It seems to have been broken for some time now,
but the fix should make it in 2.4.3 when that is ready. It should be in
cvs soon, after I run all the tests.
I spoke to
ANTON DEGUET wrote:
Daniel,
This works but I then run into a long known issue with the CMake SWIG macro,
i.e. the dependencies don't handle files included by SWIG using the %include.
I believe there is a ticket opened for this issue.
Yes, this is quite annoying. I've been looking at
Hi,
I am trying to test a shared library using cmake. In my top level
directory, I have the source directory (src), which contains the source
files to build the library, and a test directory (test), which contains
the source files to build the binaries that will be used to test the
shared
I have a simple Fortran project that I am testing with cmake.
PROJECT(multi_patch Fortran)
SET( SRCS
aAdjKeep.f
Main_mp.f
)
ADD_EXECUTABLE(multi_patch ${SRCS})
However, the first file is a Fortran 95 module and when I try to build I get
the following error.
Scanning dependencies of
One of the persons indicated that more info is required ito the problems
that I have. I am busy compiling/capturing problems, but the results are
kind of big. How should I handle that in terms of posting?
Louis.
___
CMake mailing list
Flávio P. Duarte wrote:
Hi,
I am trying to test a shared library using cmake. In my top level
directory, I have the source directory (src), which contains the source
files to build the library, and a test directory (test), which contains
the source files to build the binaries that will be
Louis Kruger wrote:
One of the persons indicated that more info is required ito the problems
that I have. I am busy compiling/capturing problems, but the results are
kind of big. How should I handle that in terms of posting?
Just cut-and-paste the portion of your log at which the first error
On 2006-07-24 11:14-0400 Brad King wrote:
If you don't set BUILD_WITH_INSTALL_RPATH or SKIP_BUILD_RPATH properties
then the modules built into the build tree will have the proper rpath to
load from there.
Thanks for that useful information which I have just confirmed. I have also
just
Alan W. Irwin wrote:
On 2006-07-24 11:14-0400 Brad King wrote:
Summary: Just set INSTALL_RPATH on the module target to be the rpath
needed in the install tree. Then things will just work.
I followed that advice for INSTALL_RPATH with libplplotd, and it worked,
but
unlike the build tree
Karl Merkley wrote:
I have a simple Fortran project that I am testing with cmake.
PROJECT(multi_patch Fortran)
SET( SRCS
aAdjKeep.f
Main_mp.f
)
ADD_EXECUTABLE(multi_patch ${SRCS})
However, the first file is a Fortran 95 module and when I try to build I get
the following
Im setting up the build environment for our project
and Ive been looking around to find some examples of how to create
CMakelists.txt files and the only examples Ive come across so far are
the trivial ones on the cmake page and the crazy convoluted ones (well, from my
novice perspective)
Hi Richard,
Richard Fuchs wrote:
Are there any other places that I can look to find some examples while I
wait for my cmake book to arrive in the mail? Any pointers would be
useful. Thanks
I found the latest Scribus (http://www.scribus.net) CVS source to be
quite helpful as an example
Richard Fuchs wrote:
Im setting up the build environment for our project
and Ive been looking around to find some examples of how to create
CMakelists.txt files and the only examples Ive come across so far are
the trivial ones on the cmake page and the crazy convoluted ones (well,
On 2006-07-24 13:22-0700 Alan W. Irwin wrote:
On 2006-07-24 11:14-0400 Brad King wrote:
If you don't set BUILD_WITH_INSTALL_RPATH or SKIP_BUILD_RPATH properties
then the modules built into the build tree will have the proper rpath to
load from there.
Thanks for that useful information which
Hello,
I'm going to begin with the usual I'm not sure this is the right
place to post this, but hopefully it is, so with that done I can get
on to my real question.
I'm trying to build a game engine, or rather what is currently there,
I'm currently developing.
The output of the build is supposed
At 09:00 PM 7/24/2006, Tilo Wiklund wrote:
Hello,
I'm going to begin with the usual I'm not sure this is the right
place to post this, but hopefully it is, so with that done I can get
on to my real question.
I'm trying to build a game engine, or rather what is currently there,
I'm currently
On 2006-07-25 03:00+0200 Tilo Wiklund wrote:
My first thought was to compile all the different parts into their own
libraries and then link them all into a common shared one. This,
apperently, wasn't possible and maybe not a very clever way to do it.
Simply having a ADD_LIBRARY with all the
21 matches
Mail list logo
