Unfortunately, I can't provide this because we had to get the builds running, and installed the proper packages. But I don't think I was imagining things.
On Wed, Feb 2, 2011 at 6:57 AM, Michael Hertling <[email protected]> wrote: > On 01/31/2011 05:26 PM, kent williams wrote: >> I found this out on a RHEL6 machine, which comes stock with tclsh and >> wish but without the C header files for development. >> >> FindTCL.cmake sets TCL_FOUND, even though >> TCL_INCLUDE_PATH:PATH=TCL_INCLUDE_PATH-NOTFOUND >> >> Imagine the hilarity that ensues! > > The FindTCL module from CMake 2.8.3 contains the line > >>> FIND_PACKAGE_HANDLE_STANDARD_ARGS(TCL DEFAULT_MSG TCL_LIBRARY >>> TCL_INCLUDE_PATH) > > so TCL_FOUND shouldn't come out as TRUE if TCL_INCLUDE_PATH isn't TRUE > also. Is the questionable FindTCL module the same as the official one? > Could you provide the complete output of a FIND_PACKAGE(TCL) resulting > in TCL_FOUND==TRUE and TCL_INCLUDE_PATH==FALSE from a clean build? > > 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 > _______________________________________________ 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
