On 2007-12-10 10:12+0100 Hendrik Sattler wrote:
Quoting "Alan W. Irwin" <[EMAIL PROTECTED]>:
Someone else also pointed out a problem with .i files having to be in
the
current source dir.
We have never felt constrained by that limitation (in fact I was unaware
of
it) since it is possible to specify just one *.i file in the current
source
directory that then includes *.i files from elsewhere in the source tree.
I could also copy the .i file multiple times but that somewhat defeats the
purpose. I have a bug open for that.
Just to clarify we do not copy *.i files or have duplicate *.i information
in multiple files for our particular swig configuration. Instead, we keep
all the common swig information (e.g., the definition of our library's API)
in one large common file which is included by our relatively small
language-specific swig *.i files.
If you are unable/unwilling to use a similar organization (small
language-specific *.i files which include *.i files with the common swig
information) and therefore are forced by the above CMake limitation to copy
*.i files for your particular swig needs, then obviously the removal of that
CMake limitation is a high priority for you.
Alan
__________________________
Alan W. Irwin
Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).
Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__________________________
Linux-powered Science
__________________________
_______________________________________________
CMake mailing list
[email protected]
http://www.cmake.org/mailman/listinfo/cmake
