On 15. Jul, 2010, at 19:14 , michael.schm...@l-3com.com wrote:
>> Did you enable the -includeall option? If so, that might be the problem
>> here. Try removing it, I just copied it from the FAQ.
>>
>> Michael
>
> For someone new to cmake, that option seems non-intuitive. Is there
> documentati
>Did you enable the -includeall option? If so, that might be the problem
>here. Try removing it, I just copied it from the FAQ.
>
>Michael
For someone new to cmake, that option seems non-intuitive. Is there
documentation I missed?
-Mike
___
Powered by
>Did you enable the -includeall option? If so, that might be the problem
>here. Try removing it, I just copied it from the FAQ.
>
>Michael
That was it. Thanks for all your help.
-Mike
___
Powered by www.kitware.com
Visit other Kitware open-source proj
On 15. Jul, 2010, at 18:09 , michael.schm...@l-3com.com wrote:
>> Never done it myself, but reading the FAQ and the docs, I'd suggest
>> something like this:
>>
>> find_package(SWIG REQUIRED)
>> include(${SWIG_USE_FILE})
>> find_package(PythonLibs REQUIRED)
>> include_directories(
>> ${CMAKE_CUR
>Never done it myself, but reading the FAQ and the docs, I'd suggest
>something like this:
>
>find_package(SWIG REQUIRED)
>include(${SWIG_USE_FILE})
>find_package(PythonLibs REQUIRED)
>include_directories(
> ${CMAKE_CURRENT_SOURCE_DIR}
> ${PYTHON_INCLUDE_DIRS}
> )
>
>set_source_files_properties(
On 14. Jul, 2010, at 22:36 , michael.schm...@l-3com.com wrote:
> Hello again,
>
> I read the FAQ on Swig generation, but I still have a couple questions.
> Here's a snippet from my original Makefile.am:
>
> mylib_la_SOURCES = swig_main.i regular.cxx swig_gen.cxx
>
> ...
>
> swig_gen.cxx : swi
Hello again,
I read the FAQ on Swig generation, but I still have a couple questions.
Here's a snippet from my original Makefile.am:
mylib_la_SOURCES = swig_main.i regular.cxx swig_gen.cxx
...
swig_gen.cxx : swig_main.i swig_a.i swig_b.i regular.h
swig -Wall $(INCLUDES) -c++ -python -o s
