Hi,
I'm still having problems with this. It seems my swig is not creating
the output directory for the swig generated cxx file. To get this to
work I have had to add a further make_directory command to the custom
command to create the required output directory before the file is swigged.
I
Finally, I have got around to this again.
My problem is that my swig files are a sibling directory of the python
where the CMakeLists.txt file is so I specify the relative path using '..'
If I try and pass through the absolute path of the swig interface files
I get a CMake error telling me it c
Hm strange.
I use the swigmodule a lot and it creates my .cxx files in the binary-dir;
but I have no relative path in the name of the
interface file.
Have you tried to use an absolute path like
set(SRC_FILE ${CMAKE_SOURCE_DIR}/swig/interface/context.i)
?
Relative paths are always a little bit cu
I am wrapping a library with SWIG and using CMake to generate the build
scripts for me, this is all working really well. My issue is the
location of the generated .cxx files.
I have my code laid out as follows:
swig/interface/*.i <-- swig interface files
python/CMakeLists.txt <-- Python CMa
