Alan,
Thanks for your help! I tried to implement that paradigm myself in a small
example CMakeLists.txt which I've attached, but the addition of a depending
custom target doesn't seem to change the context of the 'this' target. In
other words, the IS_INTERROGATE property is still read from fake_ta
On 2018-02-18 03:49-0700 Sam Edwards wrote:
However, when it came time to actually set this IS_INTERROGATE property, I
could find no way to apply it to a custom command. I guess this makes sense
- custom commands aren't targets, after all. But I couldn't convert my
custom command to a custom tar
Just to close this thread: Also the ninja tipp turned out to be a very
good one! I did the same full built (clear - rebuild) with ninja
instead of make -j4 and times were more or less comparable: from
initially 23 minutes down to 13-14 with make, and 12-13 with ninja.
However, what is much more hel
Hi list!
I'm working on a CMake buildsystem for the Panda3D project. The project is
essentially a C++ 3D engine with its own custom Python binding generator
known as Interrogate. The basic idea is that after a library's C++ code is
compiled in the usual way, the C++ source files and headers are pa