> Yes, it was meant to work with Makefiles and Ninja.
Okay, I'll give it a shot with Ninja and report back.

> Not at the moment, but C support double be just copy&paste replacing "CXX" 
> with "C". I'll add it to the TODO.
Thank you. ReactOS is mostly C so lack of its support prevents us from testing 
it on ReactOS.

I noticed two things so far:

* It seems target centric, what about targets where we want PCH to cover a 
specific set of source files, not all the source files of a target? I ask 
because in ReactOS, for example, we are forced to compile GUID related source 
files without PCH in order for them to work. Other cases can be when some 
source files requires flags/defines applied to headers that belong to the PCH 
but are not present in other source files. Is there a way to achieve that?
* The shared idea means you can create a target just to hold a PCH, then make 
the rest of targets share that PCH?

Regards,
Amine.

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Reply via email to