On 04/05/2011 06:26 PM, aaron_wri...@selinc.com wrote: > There's a base class for the dependency scanners and several derived > classes for C, java, fortan, etc. Would it not be easy to just derive > another class for each file type I need? These dependency scanner classes > seemed to just regex each line in the file looking for "include" or > "import", or some other language specific keyword. That would work for me, > I could just scan for "m4_include".
Probably, this is well feasible, but IMO, it would be really worthwhile to - optionally - enable the usage of an external tool to do dependency scanning, for new languages as well as for the premier ones like C/C++ in case one wants to overcome the built-in scanner's shortcomings while accepting certain performance penalties. There has already been some considerations and requests in this regard, e.g.: http://www.mail-archive.com/cmake@cmake.org/msg30396.html (!) http://public.kitware.com/Bug/view.php?id=11985 http://public.kitware.com/Bug/view.php?id=11770 http://public.kitware.com/Bug/view.php?id=2172 Regards, Michael _______________________________________________ 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://www.cmake.org/mailman/listinfo/cmake