On Sat, Jan 29, 2011 at 4:20 AM, Eric Noulard eric.noul...@gmail.comwrote:
2011/1/29 James Bigler jamesbig...@gmail.com:
On Jan 28, 2011, at 5:21 PM, Eric Noulard eric.noul...@gmail.com
wrote:
2011/1/29 James Bigler jamesbig...@gmail.com:
I can't seem to be able to push to stage. I
On 29. Jan, 2011, at 3:06 , Óscar Fuentes wrote:
Michael Wild them...@gmail.com 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
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 likely
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
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 158b44807f7b651366b0b34b41a8e90605ceab11 (commit)
via
