That's a pretty messy workaround though, I think. ExternalProject_Add passes in lots of variables, including ones that do not typically change, like CMAKE_CXX_COMPILER. Why impose a special requirement on the CMAKE_TOOLCHAIN_FILE variable? Would a patch to avoid the warning be a welcome change, or is there a reason the warning should remain?
Pat On Wed, Feb 6, 2013 at 9:52 PM, Michael Wild <them...@gmail.com> wrote: > Hi > > > On Wed, Feb 6, 2013 at 11:59 AM, Pat Marion <pat.mar...@kitware.com>wrote: > >> Hi, >> >> I'm emailing about bug >> 13093<http://public.kitware.com/Bug/view.php?id=13093>in the backlog. I >> found comments >> by Brad <http://www.cmake.org/pipermail/cmake/2011-February/042556.html>that >> suggest it's a legitimate warning, but I'm not sure how a project >> could avoid the warning. > > > By not specifying the toolchain file, for instance? If you have the > problem in conjunction with ExternalProject_Add, check whether the > CMakeCache.txt file exists in the build tree of the external project. If > not, include the flag, otherwise drop it. > > My 2c > > 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
