This is a question about ADD_CUSTOM_COMMAND, not SWIG, which just appears in
the introduction.
I give the command,
swig_add_module(basic csharp ${CMAKE_SOURCE_DIR}/basic.i)
And the UseSWIG.cmake makes a custom command,
add_custom_command(
DEPENDS
${CMAKE_SOURCE_DIR}/ba
> ~/build/config.h:245:5: error: missing binary operator before token "1"
>
>
> line 245 is this line
> #if HAVE_EXTENDED_PRECISION_REGISTERS
>
> Si I am perplexed where this '1' came from or indeed which '1' is being
> referred to
You probably have named your CMake variable this w
On Wednesday 26 January 2011 19:07:57 Michael Jackson wrote:
> I _think_ there are issues with generating a file that is later used by
> CMake. I think. The other issue is that every time you run CMake (by
> default) that file is going to be written, then configured by cmake which
> will most likel
On 29. Jan, 2011, at 3:06 , Óscar Fuentes wrote:
> Michael Wild writes:
>
The point I (and Andreas) wanted to make is that you can just add it. If
it's a system directory, CMake is going to filter it out (I didn't say
duplicates, I said "doesn't even show up ONCE", which means *z
