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 cannot find the source file! It is
trying to append the absolute path onto the current CMAKE_SOURCE_DIR.
Which in my case is not a substring of the absolute source file string.
If my build tree is located anywhere else, then the directory
../interface probably won't exist and the build will fail when it tries
to compile an interface file.
Thanks for you suggestion Felix.
On 09/27/12 09:42, felix wrote:
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 cumbersome; what happens if your
build tree is far away from the source tree?
Felix
--
View this message in context:
http://cmake.3232098.n2.nabble.com/SWIG-generated-cxx-file-location-issue-tp7581826p7581836.html
Sent from the CMake mailing list archive at Nabble.com.
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
