On 11/26/2013 02:23 PM, Peter Kuemmel wrote: > I'm not sure if it is a good idea to implement the pch support > completely on the C++ side
It could be a combination of C++-coded logic plus lookups of platform information variables set in Modules/Platform/*.cmake and Modules/Compiler/*.cmake files. Just about everything CMake generates works this way. > With this property we have similar solutions for msvc and gcc > which could be a starting point of a "official" pch macro. That doesn't matter because IMO the properties are not suitable for addition because they step on the toes of internal implementation details and won't work for IDEs. The reason they make the PCH rules easier to write is because they expose internal details. Direct C++-coded PCH support would be able to see these details anyway. > But ATM I don't know if these properties are usable for the IDEs. ...and as a result they won't be useable for the PCH modules either. The link Steve posted in his first response in this thread looks like a more realistic approach. -Brad -- 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: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
