On Monday 26 August 2013 20:37:52 Pau Garcia i Quiles wrote: > Hello, > > I'll do some testing, I didn't know the *Config.cmake files were that easy > to implement :-) > > If all goes well, it'll be in the next upload (3.3.0-2 or 3.3.1-1, if the > latter is released soon enough)
Hi Pau! No, saddly I was mistaken: a FooConfig.cmake defines what's the library paths, the include paths, the module version, etc, a FindFoo.cmake looks for libraries, includes, tries to detect the version, etc (Thanks Pino and PovAddict for explaining me that). Of course, this can make thinks easier, you just get to output the installed paths during the build. Of course, my test worked because the FindWt.cmake file did it's job of finding the stuff but you normally expect those paths already defined in a WtConfig.cmake file. Thanks a lot, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
signature.asc
Description: This is a digitally signed message part.
