On 2006-07-26 19:11-0400 hbabcockos1@... wrote:
> On Jul 25, 2006, at 9:15 PM, Alan W. Irwin wrote:
>> At the present time I would like to consolidate this achievement by
>> concentrating on dealing with bug reports for a while as other developers
>> here try it on the platforms (especially Mac OS X and bare windows)
>> accessible to you. This platform testing is the highest priority at the
>> present time, but contributions helping to fill in the missing pieces
>> above would be most welcome as well.
> Where does one get a recent version of ccmake (the cmake configuration tool)?
It's an integral part of the cmake package when you build it from unix
linefeed source at http://www.cmake.org/HTML/Download.html. So, for
example, when I built and installed cmake-2.4.2 (note that version is
necessary) here is the result in my installprefix/bin
ccmake* cmake* cpack* ctest*
Presumably, binary sources of CMake-2.4.2 (e.g.,"Darwin Universal (Tiger
only installer)") from the same download page will give you ccmake as well,
but if not, build cmake from the Unix tarball following the directions
> Or, optionally, how does one disable bindings to certain languages? I'm
> getting an error message at "make" that I suspect comes from the Fortran
> binding but I can't figure out how to disable Fortran. Use the appropriate
-D options to cmake, e.g.,
cmake -DENABLE_f77=OFF -DENABLE_f95
You can also use the cmake -LAH option to list out all options.
cmake --help-full |less
to get the details about this option and many other aspects of cmake.
The -LAH option is equivalent to ./configure --help. However, your instinct
to use the ccmake CLI is a good one since that is more convenient then
listing out all options and then entering them with -D command-line
> Also, any idea why cmake wouldn't be able to find swig, when I have swig in
For problems like yours where CMake is not finding stuff that is on your
system, the short answer is to set the environment variables
CMAKE_INCLUDE_PATH and CMAKE_LIBRARY_PATH (see
http://www.cmake.org/Wiki/CMake_Useful_Variables which I document in
In more detail, have a look at $prefix/share/CMake/Modules/FindSWIG.cmake.
(That directory is an excellent place to get information on questions like
yours.) In that file you will see a number of checks done before it even
attempts to find the swig executable.
The first part of the file is
If both of these fail to set the SWIG_DIR variable to a valid path, then you
will get no further because of the last IF test. For my platform,
SWIGConfig.cmake does not exist but swig.swg does as
/usr/share/swig1.3/swig.swg so I am okay. In your case, you may have to set
one of CMAKE_FRAMEWORK_PATH, CMAKE_APPBUNDLE_PATH, or CMAKE_INCLUDE_PATH to
find a complete version of swig with either SWIGConfig.cmake (preferred) or
swig.swg. See the results from
cmake --help-full |less
for many more details about the full directory search list that FIND_PATH
and the many other FIND_* commands use, and how you can modify that search
> Is there a (swig) version dependency?
Not explicitly. However, those files above must exist, and it is likely
versions of swig before 1.3.x did not have them. I have considered putting
in a separate swig version check, but I am not sure that is necessary since
I doubt anyone is still using swig versions prior to the 1.3.x series.
BTW, if cmake fails to find swig, your PLplot build should proceed to a
successful conclusion with the java and python interfaces smoothly disabled.
Is that the case?
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 Yorick front-end to PLplot (yplot.sf.net); the
Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project