On 02/11/2014 01:12 PM, Darrell Anderson wrote: > I don't know how we should audit the cmake conversion process. > Possibly one way is search the source tree in the known conversions > for Makefile.am and look for a coexisting CMakeLists.txt. That does > not mean the conversion is complete but would expose certain > incomplete conversions as I discovered last night in tdepim. > > We need a way to audit cmake conversions. Any ideas? Well, I did a cursory test ages ago just to get a handle on what had CMakeLists.txt and what didn't. If we could identify solid criteria like you suggested "directories with both CMakeLists and Makefile.am" files, then it would be a simple process of walking the git tree with 'find' and identifying apps which met the checks and those that partially met and those that were just autofoo. One issue I see is the use of .in.in and .in instead of .am, so we may need a fairly broad search of the variants of Makefile.am, configure.blah to get a valid picture of the state of the build setup. I'll look for some tests, if you can think of others, let us know. Everybody else as well. -- David C. Rankin, J.D.,P.E.