On 6/7/2012 10:43 AM, Peter Kümmel wrote:
Yes, I also think a solution on the cmake side make things much easier.
What about using cmake's build-in dependency parser. AFAIK there is one.
Could it be called by the command line?
I think it might be quicker to grab the cldep wrapper and try that. The
CMake one works on whole targets and does not forward the call to the
compiler. ninja seems to want to call one thing that does depends and
the compile. Either way could be done. However, just grabbing the
cldep thing from that branch might be the quickest. Although, I suspect
that this problem will show up with other non-gnu compilers, and a pure
cmake implementation would be nice to have. I don't know enough ninja
to know if it has to be done in the same command as the compile to get
it to work.
-Bill
--
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
