MantisBT - CMake
View Issue Details
0011781CMakeModulespublic2011-02-01 04:522016-06-10 14:31
Frerich Raabe 
Kitware Robot 
normalmajoralways
closedmoved 
x86Microsoft Windows7
CMake 2.8.3 
 
0011781: FindTCL.cmake misses opporturnities to find tclsh on Windows
I'm using ActiveTcl on Windows 7 and noticed that the FindTCL.cmake module fails to locate 'tclsh.exe' for me - but only on the first cmake run. Re-running cmake immediately causes tclsh.exe to be found successfully.
1. Run 'cmake' on the following CMakeLists.txt file:

    cmake_minimum_required( VERSION 2.8 )
    set( CMAKE_MODULE_PATH ${CMAKE_SOURCE_DIR}/cmake )

    find_package(TCL)

2. For me, it successfully finds TCL but it does not find tclsh (since it's not in my path and not in my registry either).

3. Re-run cmake as in step 1)

4. At this point, tclsh is found
A simple workaround (which I'm using right now) to resolve this problem for me is to just use

    find_package(TCL)
    find_package(TclSh)

I investigated a bit more and noticed that FindTclsh.cmake references a number of variables which are only set in FindTCL.cmake (but *after* FindTclsh.cmake is included). In particular, all of the following variables (this is a quote from FindTclsh.cmake):

    SET(TCLTK_POSSIBLE_BIN_PATHS
      "${TCL_INCLUDE_PATH_PARENT}/bin"
      "${TK_INCLUDE_PATH_PARENT}/bin"
      "${TCL_LIBRARY_PATH_PARENT}/bin"
      "${TK_LIBRARY_PATH_PARENT}/bin"
      "${TK_WISH_PATH_PARENT}/bin"
      )

No tags attached.
Issue History
2011-02-01 04:52Frerich RaabeNew Issue
2012-08-11 11:09David ColeStatusnew => backlog
2012-08-11 11:09David ColeNote Added: 0030227
2016-06-10 14:28Kitware RobotNote Added: 0041792
2016-06-10 14:28Kitware RobotStatusbacklog => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:28Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0030227)
David Cole   
2012-08-11 11:09   
Sending old, never assigned issues to the backlog.

(The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...)

If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^]

It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.
(0041792)
Kitware Robot   
2016-06-10 14:28   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.