[Insight-developers] Re: [cable] Include-Paths during CSWIG generation

[Brad King]

On Wed, 17 Dec 2003, Bertram Herzog wrote:

> I'm trying to use the current CSWIG from a cvs-checkout of the itk1.4 as
> of the beginning of december to make the enclosed examples and some more
> medical imaging software run and be accessible from Tcl.
>
> My configuration:
> Windows XP home, Visual C++ 6.0 SP5
> CMake 1.9 (cvs-checkout from 2003-11-12)
> CSWIG and CABLE and GCC_XML from itk1.4-cvs checkout as of  2003-12-04
>
> My current problem is:
> When using the simple String-example, my Visual C complains on compiling
> StringConfigTcl.cxx in the WrapString-Project that it can't find the
> system include file <tcl>. When included by hand as
> "C:\Tcl\include\tcl.h", it compiles.
> The only problem is: the file StringConfig.cxx is the standard one and
> seems ok, then it gets CSWIGged and transforms into StringConfigTcl.cxx,
> according to the CMakeLists.txt in /Testing/String.
> This file, which is automatically generated by CSWIG, has the #include
> <tcl> directive.
>
> I suggest, that a) my Tcl-Include directory is not set as an environment
> variable in XP or Visual C,
> or b) the Tcl-Include-Path from the CMakeCache is not used correctly to
> build the CSWIG output. (sure, I hope for the latter ;-) )
> Any ideas or suggestions?

The examples on the CABLE web page have never been tested with CableSwig
and are not supported.  I think your problem is (b).

> Another question: I understand, that CSWIG is temporary and should
> result in a "gcc-xml-to-direct-SWIG" one day, and that documentation is
> the worst paid part of a sw-development process. But in the early days
> of CABLE there was a Graphic on one of the web-pages depicting the whole
> development process, and the way the files get handled by gcc-xml, CABLE
> and CMake. Is there anything comparable for the momentary build using
> CSWIG? It might help when digging through the code and tracing errors.

I do not think any such document was created.  Unfortunately we do not
have time to support CableSwig as a separate project outside the ITK
wrapping process.  This is why documentation has not been created.

-Brad