On Thu, 5 Feb 2004, Alexander Hansen wrote:
Does setting your environment as per
http://fink.sourceforge.net/faq/usage-general.php#compile-myself
work?
Nope. That works for the few programs that I've done that use
./configure, but in this particular case (EMAN), cmake isn't reading them.
I've entered the locations manually for now, but it'd be nice to not have
to do it all the time and let cmake find them.
What version of cmake are you using? In cmake-1.8.3-1, I replace almost all occurrencies of /usr/local by /sw, so that cmake already finds some of the fink stuff on its own.
But cmake is not exactly equivalent to configure. And even for configure, you often have to set additional options besides --prefix=/sw. Actually, the CFLAGS and LDFLAGS you mentioned have not much influence on configure, they are used in the "make" phase for the cases where configure didn't find out the right paths. For finding out these paths, configure often needs other options such as --with-extra-includes=/sw/include, --libexecdir=/sw/lib, --with-qt-includes=/sw/include/qt and so on (I chose some arbitrary examples from actually existing Fink packages). This is not that different from cmake if you use it from the command line.
What sets cmake apart is its interactive configuration possibility using ccmake. I consider this rather as a curiosity. If you want to build a serious project, you can run cmake from the command line just as you run configure from the command line. Instead of a line (this is again extracted from existing Fink packages)
./configure --prefix=/sw --with-qt-dir=/sw --with-qt-includes=/sw/include/qt --with-qt-libraries=/sw/lib --with-extra-includes=/sw/include --with-extra-libs=/sw/lib --with-pythondir=/sw/lib/python2.3
you get a line of the type
./cmake -DCMAKE_INSTALL_PREFIX:PATH=/sw -DTCL_INCLUDE_PATH:PATH=/sw/include -DTCL_LIBRARY:FILEPATH=/sw/lib/libtcl.dylib -DTK_INCLUDE_PATH:PATH=/sw/include -DTK_INTERNAL_PATH:PATH=/sw/include/vtk/tkInternals/tk84OSX -DPYTHON_EXECUTABLE:FILEPATH=/sw/bin/python2.3 -DPYTHON_INCLUDE_PATH:PATH=/sw/include/python2.3 .
and so on. The question whether one of the options, "--prefix=/sw" in the case of configure, is already predefined by Fink, is rather irrelevant in this case. Which one would you like to have predefined in the case of cmake? CMAKE_INSTALL_PREFIX:PATH=/sw perhaps? Or some others?
Then, of course, cmake does more than configure. It also plays the roles of autoconf, automake, and libtool to a certain extent. Fine-tuning these to the needs of Mac OS X and then of Fink has been and still is a lengthy process. The cmake modules are already more or less Mac OSX-aware. Teaching them what they need to know about Fink is certainly important, but I think this is not done by just predefining one or two environment variables.
This would require first and foremost some knowledgable people who know both Fink and cmake plus some of the packages that use cmake for their compilation. I am pretty much a newbie in this respect, and I haven't yet seen anyone coming forward with skills in this direction, apart from the maintainer of the older versions of cmake, but he seems to have disappeared.
-- Martin
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
