On 10/03/2012 07:57 PM, Dan Furlani wrote:
#ifndef CODEGEN
#include GeneratedFile.h
#endif
As you point out CMake does not actually preprocess the sources.
You can hide includes from it like this:
#ifndef CODEGEN
# define CODEGEN_GeneratedFile_h GeneratedFile.h
# include
As you point out CMake does not actually preprocess the sources.
You can hide includes from it like this:
Hi Brad,
Thanks for the response. I considered that, it would solve the
problem for the codegen, but then CMake wouldn't be aware of the
(legitimate) dependency when it builds the program
On 10/04/2012 12:38 PM, Dan Furlani wrote:
Thanks for the response. I considered that, it would solve the
problem for the codegen, but then CMake wouldn't be aware of the
(legitimate) dependency when it builds the program code.
If you hide it behind a function-like macro then you can use
the
If you hide it behind a function-like macro then you can use
the IMPLICIT_DEPENDS_INCLUDE_TRANSFORM to tell the targets
where you want the dependency how to get it:
Thanks, that worked. Here's what I had to do, maybe there was an
easier way I missed.
1. Define macros MY_ADD_LIBRARY and
Hi,
I'm having issues with the way CMake scans for dependencies. It's causing
unpredictable rebuilds of my project which means I need to run 'make'
multiple times (until nothing rebuilds) before I can 'sudo make install'.
The project incorporates a code generator. It parses all C++ header
Looking at the mail archive it appears that my message was cut off. The
remainder:
From a compile standpoint, there is no problem -- the codegen is built with
-DCODEGEN so it won't include the generated file, which of course wouldn't
even exist on the first pass. But since CMake doesn't
Hmm, having trouble emailing the list. Full question is here:
http://pastebin.com/riWe6zX7
--
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:
