On Tue, Mar 1, 2011 at 11:21, Phil Blundell <[email protected]> wrote: > On Wed, 2011-02-23 at 13:47 +0000, Otavio Salvador wrote: >> In any case cmake will know the "internal" modules directory by itself >> so it works even if this value doesn't match. This is where it is >> going to look as fallback and I was using 2.8 without 2.6 for long >> time without noticing any issue. >> >> This seems safe. We could drop the CMAKE_MODULE_PATH if preferred. I >> just fixed it to 2.8 to reflect the current default one. > > If I understand right, you're saying that the CMAKE_MODULE_PATH doesn't > serve any useful purpose since cmake works just fine without it. If > that's the case then yes, let's just drop it altogether.
I'll make this change locally and see if it works fine for a build from scratch. In this case, I post the patch. -- Otavio Salvador O.S. Systems E-mail: [email protected] http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
