[CMake] CMake and SWIG

[Caron, Michael C. (US SSA)]

That is exactly what I had tried (thanks for confirming that things work the way I think) at first.  I didn't try the SET(...) but I did put the full path to SWIG in my PATH.  Since that should have worked I tried something else.  I usually run from a .bat file on windows and an equivalent shell script on linux.  When I run the .bat file by double clicking from an explorer window I get no dice.  But if I run the same .bat file from the command line life is good.  It turns out the explorer window was open before I changed the environment variable and it didn't pick up the environment change for any of its children.  I really hate it when I'm stupid.

Thanks for the nudge,
Michael Caron
Principle Software Engineer
Systems Development Center
BAE Systems, NA
95 Canal St.
Nashua, NH 03064
T:603-885-2096
E:michael.caron at baesystems.com

From: David Cole [mailto:david.cole at kitware.com]
Sent: Thursday, March 18, 2010 4:16 PM
To: Caron, Michael C. (US SSA)
Cc: cmake at cmake.org
Subject: Re: [CMake] CMake and SWIG

If you open the file "C:/Program Files/CMake 2.8/share/cmake-2.8/Modules/FindSWIG.cmake" and read through it, you will see exactly where CMake is looking for SWIG.

It uses:

FIND_PROGRAM(SWIG_EXECUTABLE swig)

(which means it's only looking in the PATH...)

So you can either:

  set(SWIG_EXECUTABLE "C:/full/path/to/swig.exe")
  # (before FIND_PACKAGE(SWIG REQUIRED))

or:

  have swig.exe available somewhere in the PATH environment variable...


HTH,
David

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20100319/46d181de/attachment.htm>