[Insight-developers] Re: problem with cableswig when sources are
removed
Gaetan Lehmann
gaetan.lehmann at jouy.inra.fr
Wed Dec 7 12:31:54 EST 2005
On Wed, 07 Dec 2005 17:27:05 +0100, Brad King <brad.king at kitware.com>
wrote:
> Gaetan Lehmann wrote:
>> Hi Brad,
>> CableSwig seems to search files only in source dir, and so, can't run
>> when sources are deleted:
>> Generating swigrunPython.cxx
>> cd
>> /home/glehmann/rpm/BUILD/InsightToolkit-2.4.0/Wrapping/CSwig/SwigRuntime
>> && /usr/bin/cswig -o
>> /home/glehmann/rpm/BUILD/InsightToolkit-2.4.0/Wrapping/CSwig/SwigRuntime/swigrunPython.cxx
>> -python -c++
>> /home/glehmann/rpm/BUILD/InsightToolkit-2.4.0/Wrapping/CSwig/SwigRuntime/swigrun.xml
>> Cannot find SWIG Lib directory. Checked:
>> /export/home/mandrake/rpm-rebuilder/RPM/BUILD/CableSwig/SWIG/Lib
>
> I'll assume you're talking about an installed CableSwig tree in which
> the source has been deleted.
That's it :-)
> It is supposed to look in the install location for the SWIG/Lib
> directory.
SWIG/Lib ?
I have a SWIGLib dir, but no SWIG/Lib
/usr/lib/CableSwig/SWIGLib/
> In the file
>
> SWIG/Source/Include/swigconfig.h.cmake.in
>
> the line
>
> #cmakedefine SWIG_LIB_INSTALL "@SWIG_LIB_INSTALL@"
>
> appears. It is supposed to get configured to the install location of
> the SWIG library. Then in Executables/cableSwigMain.cxx there is code
> that looks for the library there if SWIG_LIB_INSTALL is defined. Check
> your build tree to see if the header was properly configured.
>
it is not defined.
I try to force it with cmake
> This install support is very minimal and hard-codes the full-path to the
> install location. It also prefers looking in the source tree even when
> running from the install tree. Really it should look relative to the
> executable location in the install tree to find the library but we've
> not had time to implement this.
>
> -Brad
--
Gaëtan Lehmann
Biologie du Développement et de la Reproduction
INRA de Jouy-en-Josas (France)
tel: +33 1 34 65 29 66 fax: 01 34 65 29 09
http://voxel.jouy.inra.fr
More information about the Insight-developers
mailing list