Re: [CMake] on find_package and building dependencies
2011/12/29 Ryan Lewis m...@ryanlewis.net: Hi, I really like CMake's find_package() utility for finding dependencies, but for some projects I have a separate local copy of the installed libraries, and I want to point find_package at a particular directory to find the installed libraries. How can I do this? Have a look at find_package documentation, in particular the usage of CMAKE_FIND_ROOT_PATH and other *CMAKE_FIND_ROOT_PATH_* variables you basically want: set(CMAKE_FIND_ROOT_PATH /you/local/install/dir) before calling find_package(...) On that note, I also have some dependencies which themselves are build using CMake, it is possible to tell my CMake Project to build another CMake project? Yes, cmake --help-module ExternalProject and the macro therein ExternalProject_Add note that you may simply want to export the target of the first project and then import the targets into the referring project, on that case have a look at: http://www.cmake.org/Wiki/CMake/Tutorials/Exporting_and_Importing_Targets -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] on find_package and building dependencies
2011/12/29 Ryan Lewis m...@ryanlewis.net: Hi, your suggestion on setting that variable before a find_package() just simply _is not_ doing what I expect. I specify my own location of libz and it _always_ finds the system wide version. Then there must be something weird, did you clean-up your build tree before testing? You may try in a fresh new pristine build tree. Would you be able to try the attached project and replace the set(CMAKE_FIND_ROOT_PATH /home/erk/TestZlib/installed) with an appropriate value for your config. You must start from a fresh new build tree. Also I cannot get the ExternalProject_Add() module to work properly. I'll try to answer that separately. Beware not to drop the CMake ML address. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org usezlib.tgz Description: GNU Zip compressed data -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] How to install then test?
Dear All! Maybe someone can help me: I have a project, we compile binaries and then using various INSTALL directives finish the job by copying files where they belong: to bin, man, libexec, etc. The point is, we need to run executables after they got installed into this tree, because otherwise they won't find all auxiliary files during runtime. So I am really missing the point here: how to install files (to a temporary directory, for example) and then run various tests? Maybe someone has ideas... Sincerely, Denis -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Using ExternalProject_Add
2011/12/29 Ryan Lewis m...@ryanlewis.net:
[...]
Also I cannot get the ExternalProject_Add() module to work properly.
include(ExternalProject)
ExternalProject_Add( JPEG
PREFIX ${CURRENT_SOURCE_DIR}
CURRENT_SOURCE_DIR is probably a typo:
you certainly mean:
CMAKE_CURRENT_SOURCE_DIR
[...]
This command is also creating a folder structure called JPEG-prefix
which does not seem to contain relevant/useful content..
What am I doing wrong?
The typo, ${CURRENT_SOURCE_DIR} evaluate to empty string .
try that:
include(ExternalProject)
ExternalProject_Add(MyZLib
PREFIX /tmp/TestZlib/1.2.5
URL http://zlib.net/zlib-1.2.5.tar.bz2;
URL_MD5 be1e89810e66150f5b0327984d8625a0
PATCH_COMMAND ${CMAKE_COMMAND} -E remove -f
SOURCE_DIR/zconf.h
CMAKE_ARGS
-DCMAKE_INSTALL_PREFIX=/tmp/TestZlib/1.2.5/installed
)
it should download and locally install zlib during the first build.
Note that you cannot use ExternalProject_Add in order to download build
a local dependency of the currently built project because it will be invoked
**at build time** so that at CMake **first-time** (when you configure
your project for the first time)
the external project is not build yet.
I suggest you read at least some mailing threads about ExternalProject_Add usage
they should be enlightening:
http://www.cmake.org/pipermail/cmake/2011-September/046423.html
http://www.cmake.org/pipermail/cmake/2011-September/046233.html
http://www.cmake.org/pipermail/cmake/2011-September/046360.html
--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Per-configuration include directories?
Thanks. I just worked around it by checking the generator for visual studio and then doing something like: include_directories (path_to_lib/$(Outdir)/include) That works at least in VS. I may have to do a similar thing with link_directories. Kevin On 12/29/2011 11:18 AM, Robert Dailey wrote: I was asking about this a couple of weeks ago. David Cole has expressed interest, and it seems it has been placed on the roadmap to implement this feature. However, for the time being this can't be done. There are a couple of workarounds I know of, but none of which are CMake workarounds. I've had to use preprocessor conditions in my source files to turn certain ones on or off depending on my configuration. - Robert Dailey On Thu, Dec 29, 2011 at 10:48 AM, Kevin Burge kevin.bu...@systemware.com mailto:kevin.bu...@systemware.com wrote: I'm trying to get my large project (built of many sub-projects and external projects) to build correctly in Visual Studio, allowing the user to compile release/debug from the UI. One problem I have: I'm building an external library, and I've customized ExternalProject to keep per-configuration builds of the external projects. The problem I'm now facing that I don't see a resolution to: I need include_directories to allow per-configuration includes. I.e. include_directories (third_party_INCLUDE_DIR_DEBUG) or include_directories (third_party_INCLUDE_DIR_RELEASE) I tried setting COMPILE_FLAGS with -I... for the target, but cmake seems to ignore that when generating the Visual Studio 2005 project files. There doesn't seem to be a way to force the include into the visual studio project files. Is there a way I can do this? Thanks, Kevin -- Powered by www.kitware.com http://www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Per-configuration include directories?
I was asking about this a couple of weeks ago. David Cole has expressed interest, and it seems it has been placed on the roadmap to implement this feature. However, for the time being this can't be done. There are a couple of workarounds I know of, but none of which are CMake workarounds. I've had to use preprocessor conditions in my source files to turn certain ones on or off depending on my configuration. - Robert Dailey On Thu, Dec 29, 2011 at 10:48 AM, Kevin Burge kevin.bu...@systemware.comwrote: I'm trying to get my large project (built of many sub-projects and external projects) to build correctly in Visual Studio, allowing the user to compile release/debug from the UI. One problem I have: I'm building an external library, and I've customized ExternalProject to keep per-configuration builds of the external projects. The problem I'm now facing that I don't see a resolution to: I need include_directories to allow per-configuration includes. I.e. include_directories (third_party_INCLUDE_DIR_**DEBUG) or include_directories (third_party_INCLUDE_DIR_**RELEASE) I tried setting COMPILE_FLAGS with -I... for the target, but cmake seems to ignore that when generating the Visual Studio 2005 project files. There doesn't seem to be a way to force the include into the visual studio project files. Is there a way I can do this? Thanks, Kevin -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/** opensource/opensource.htmlhttp://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/**CMake_FAQhttp://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/**listinfo/cmakehttp://www.cmake.org/mailman/listinfo/cmake -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] How to install then test?
2011/12/29 Denis Scherbakov denis_scherba...@yahoo.com:
Dear All!
Maybe someone can help me: I have a project, we compile binaries and then
using various INSTALL directives finish the job by copying files where they
belong: to bin, man, libexec, etc. The point is, we need to run
executables after they got installed into this tree, because otherwise
they won't find all auxiliary files during runtime.
What do you mean by auxiliary files ?
If auxiliary files are shared libs they should be found just fine for
the executable in the build tree
(see http://www.vtk.org/Wiki/CMake_RPATH_handling)
Moreover add_test accepts $ generator expressions
which may helps you to specify complete path to files produced by your build.
So I am really missing the point here: how to install files (to a temporary
directory, for example) and then run various tests? Maybe someone has ideas...
In any case,
if you want to install to a temp dir you can use a custom command/target
which use DESTDIR, like in
make DESTDIR=/tmp install
(I suppose you use Makefile generator in this case)
You can suppose that the user/developer should (explicitely) call some
custom target
add_custom_target(TempInstall ${CMAKE_BUILD_TOOL}
DESTDIR=${CMAKE_BINARY_DIR}/tempInstall
COMMENT Install to temporary location
for testing purpose)
that will install the needed file in a temps location and then use a
test driver programs or scripts
which may be informed of the temp install dir
add_test(NAME mytest1
COMMAND testDriver --tmp-install-dir
${CMAKE_BINARY_DIR}/tempInstall --test=test1)
add_test(NAME mytest2
COMMAND testDriver --tmp-install-dir
${CMAKE_BINARY_DIR}/tempInstall --test=test2)
testDriver may itself be built/created by your build process.
with this you have to do:
make TempInstall
make test
in order to run the test properly.
It would be nice to have a way to make test depends on TempInstall
but I do not know
a way to do that: http://public.kitware.com/Bug/view.php?id=8438
--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
[CMake] Per-configuration include directories?
I'm trying to get my large project (built of many sub-projects and external projects) to build correctly in Visual Studio, allowing the user to compile release/debug from the UI. One problem I have: I'm building an external library, and I've customized ExternalProject to keep per-configuration builds of the external projects. The problem I'm now facing that I don't see a resolution to: I need include_directories to allow per-configuration includes. I.e. include_directories (third_party_INCLUDE_DIR_DEBUG) or include_directories (third_party_INCLUDE_DIR_RELEASE) I tried setting COMPILE_FLAGS with -I... for the target, but cmake seems to ignore that when generating the Visual Studio 2005 project files. There doesn't seem to be a way to force the include into the visual studio project files. Is there a way I can do this? Thanks, Kevin -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Per-configuration include directories?
It won't be necessary with link_directories because you can specify absolute paths to your LIB files in target_link_libraries(). You can also specify 'debug' or 'optimized' prior to the lib. for example: target_link_libraries( myproject debug C:/project/libs/debug/zlib.lib optimized C:/project/libs/release/zlib.lib ) - Robert Dailey On Thu, Dec 29, 2011 at 11:23 AM, Kevin Burge kevin.bu...@systemware.comwrote: Thanks. I just worked around it by checking the generator for visual studio and then doing something like: include_directories (path_to_lib/$(Outdir)/include) That works at least in VS. I may have to do a similar thing with link_directories. Kevin On 12/29/2011 11:18 AM, Robert Dailey wrote: I was asking about this a couple of weeks ago. David Cole has expressed interest, and it seems it has been placed on the roadmap to implement this feature. However, for the time being this can't be done. There are a couple of workarounds I know of, but none of which are CMake workarounds. I've had to use preprocessor conditions in my source files to turn certain ones on or off depending on my configuration. - Robert Dailey On Thu, Dec 29, 2011 at 10:48 AM, Kevin Burge kevin.bu...@systemware.comwrote: I'm trying to get my large project (built of many sub-projects and external projects) to build correctly in Visual Studio, allowing the user to compile release/debug from the UI. One problem I have: I'm building an external library, and I've customized ExternalProject to keep per-configuration builds of the external projects. The problem I'm now facing that I don't see a resolution to: I need include_directories to allow per-configuration includes. I.e. include_directories (third_party_INCLUDE_DIR_DEBUG) or include_directories (third_party_INCLUDE_DIR_RELEASE) I tried setting COMPILE_FLAGS with -I... for the target, but cmake seems to ignore that when generating the Visual Studio 2005 project files. There doesn't seem to be a way to force the include into the visual studio project files. Is there a way I can do this? Thanks, Kevin -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Per-configuration include directories?
I used the debug and optimized just as you said. Thank you! On 12/29/2011 2:14 PM, Robert Dailey wrote: It won't be necessary with link_directories because you can specify absolute paths to your LIB files in target_link_libraries(). You can also specify 'debug' or 'optimized' prior to the lib. for example: target_link_libraries( myproject debug C:/project/libs/debug/zlib.lib optimized C:/project/libs/release/zlib.lib ) - Robert Dailey -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] on find_package and building dependencies
Thanks a bunch, Is there a way to hand this to cmake on the command line (i.e. an ExternalProject_Add), when I test on the command line with: cmake -DCMAKE_FIND_ROOT_PATH=... it gives me the warning that it is ignoring my define. -rhl On Thu, Dec 29, 2011 at 1:29 PM, Eric Noulard eric.noul...@gmail.com wrote: 2011/12/29 Ryan Lewis m...@ryanlewis.net: Hi, your suggestion on setting that variable before a find_package() just simply _is not_ doing what I expect. I specify my own location of libz and it _always_ finds the system wide version. Then there must be something weird, did you clean-up your build tree before testing? You may try in a fresh new pristine build tree. Would you be able to try the attached project and replace the set(CMAKE_FIND_ROOT_PATH /home/erk/TestZlib/installed) with an appropriate value for your config. You must start from a fresh new build tree. Also I cannot get the ExternalProject_Add() module to work properly. I'll try to answer that separately. Beware not to drop the CMake ML address. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] FTP client in CMake?
I don't think I've seen a way to use CMake to download files from an FTP server. For certain third party libraries, I'd like to store them on an FTP server and use CMAKE_COMMAND to invoke CMake.exe from within a cmake script to download the files from that FTP server. Is it possible to add this functionality? Could anyone recommend a workaround? - Robert Dailey -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] FTP client in CMake?
Hi, Doesn't file(DOWNLOAD ... ) work for you? On Fri, Dec 30, 2011 at 12:01 AM, Robert Dailey rcdai...@gmail.com wrote: I don't think I've seen a way to use CMake to download files from an FTP server. For certain third party libraries, I'd like to store them on an FTP server and use CMAKE_COMMAND to invoke CMake.exe from within a cmake script to download the files from that FTP server. Is it possible to add this functionality? Could anyone recommend a workaround? -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer) -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] FTP client in CMake?
file(DOWNLOAD ...) works with ftp: urls.
For example, the following script works for me (with CMake 2.8.6):
get_filename_component(dir ${CMAKE_CURRENT_LIST_FILE} PATH)
file(DOWNLOAD
ftp://ftp.cs.brown.edu/pub/benchmark.ps.Z;
${dir}/benchmark.ps.Z
)
I found a small file on the first server mentioned by google when searching
for public anonymous ftp server
HTH,
David
On Thu, Dec 29, 2011 at 6:01 PM, Robert Dailey rcdai...@gmail.com wrote:
I don't think I've seen a way to use CMake to download files from an FTP
server. For certain third party libraries, I'd like to store them on an FTP
server and use CMAKE_COMMAND to invoke CMake.exe from within a cmake script
to download the files from that FTP server.
Is it possible to add this functionality? Could anyone recommend a
workaround?
-
Robert Dailey
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] FTP client in CMake?
You could use wget or curl to download files. Best Regards NoRulez Am 30.12.2011 um 00:01 schrieb Robert Dailey rcdai...@gmail.com: I don't think I've seen a way to use CMake to download files from an FTP server. For certain third party libraries, I'd like to store them on an FTP server and use CMAKE_COMMAND to invoke CMake.exe from within a cmake script to download the files from that FTP server. Is it possible to add this functionality? Could anyone recommend a workaround? - Robert Dailey -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CMake 2.8.7-rc2 ready for testing!
On Tue, Dec 27, 2011 at 3:34 PM, Alan W. Irwin ir...@beluga.phys.uvic.cawrote: On 2011-12-21 20:42-0500 David Cole wrote: The CMake 2.8.7 release candidate stream continues! You can find the source and binaries here: http://www.cmake.org/files/v2.**8/?C=M;O=Dhttp://www.cmake.org/files/v2.8/?C=M;O=D This will become the final build of CMake 2.8.7 next Wednesday unless somebody finds and reports a showstopping (crasher, serious behavioral regression) issue between now and then. Hi Dave: Sorry for responding so late for your call for testing. A simple test I did for PLplot seems fine, but from an additional test with FreeEOS I just discovered there is still a potentially nasty regression for FindLAPACK.cmake/FindBLAS.**cmake from the good behavour we had for 2.8.5. The issue is that if I set CMAKE_LIBRARY_PATH to find a special version of lapack/blas, only the lapack part of that is honored. For example, if I set export CMAKE_LIBRARY_PATH=/home/**software/lapack/install_**double/lib Then here are the relevant cache results for 2.8.7 irwin@raven grep BLAS CMakeCache.txt |grep -v ADV |grep -v NOTFOUND BLAS_atlas_LIBRARY:FILEPATH=/**usr/lib/libatlas.so.3gf BLAS_f77blas_LIBRARY:FILEPATH=**/usr/lib/libf77blas.so.3gf BLAS_f77blas_atlas_WORKS:**INTERNAL=1 irwin@raven grep LAPACK CMakeCache.txt |grep -v ADV | grep -v NOTFOUND LAPACK_lapack_LIBRARY:**FILEPATH=/home/software/** lapack/install_double/lib/**liblapack.a LAPACK_lapack_WORKS:INTERNAL=1 The resulting LAPACK_LIBRARIES uncached variable is LAPACK_LIBRARIES = /home/software/lapack/install_**double/lib/liblapack.a;/usr/** lib/libf77blas.so.3gf;/usr/**lib/libatlas.so.3gf i.e., a mixture between the very latest lapack results and older system version blas results that I don't want. This inconsistent mixture of libraries (which are for different versions of lapack/blas and probably different compile flags as well) potentially could be a complete disaster. This odd combination of libraries actually worked for my particular (FreeEOS) case, but I think that might be an artifact of building and installing only static versions of lapack/blas in the CMAKE_LIBRARY_PATH location. In comparison here are the relevant cache results for 2.8.5 irwin@raven grep BLAS CMakeCache.txt |grep -v ADV |grep -v NOTFOUND BLAS_blas_LIBRARY:FILEPATH=/**home/software/lapack/install_** double/lib/libblas.a BLAS_blas_WORKS:INTERNAL=1 irwin@raven grep LAPACK CMakeCache.txt |grep -v ADV |grep -v NOTFOUND LAPACK_lapack_LIBRARY:**FILEPATH=/home/software/** lapack/install_double/lib/**liblapack.a LAPACK_lapack_WORKS:INTERNAL=1 The resulting LAPACK_LIBRARIES uncached variable is LAPACK_LIBRARIES = /home/software/lapack/install_**double/lib/liblapack.a;/home/** software/lapack/install_**double/lib/libblas.a which is exactly what I want, i.e., no chance for inconsistency between lapack and blas libraries. There is probably some quick fix you can do to get FindBLAS.cmake to properly honor CMAKE_LIBRARY_PATH, but since it is so late in the release cycle there is not much chance to test such a change. Note an extreme degree of caution is warranted for changes in FindLAPACK.cmake/FindBLAS.**cmake because there are so many different variants of those libraries available on various platforms. Furthermore, the new versions of FindLAPACK.cmake/FindBLAS.**cmake that were introduced for 2.8.6 have already had two bugs fixed, with this additional library inconsistency issue still to be fixed. So these new versions of the find modules don't appear to be completely matured yet, and my recommendation would therefore be to revert back to the time-tested versions of FindLAPACK.cmake/FindBLAS.**cmake for 2.8.5 for your 2.8.7 release, and re-introduce the new (with all known issues fixed) versions of these modules for the next release cycle to give them some additional testing before the next release. 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); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); 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 __ I've considered your plea, but after looking at the diffs between 2.8.5 and 2.8.7-rc2, I think we ought to keep what we have and continue moving forward with it. The commits involved are easily seen with these git commands: $ gitk v2.8.5..a1c9de56 -- Modules/FindLAPACK.cmake Modules/FindBLAS.cmake $ git log --oneline v2.8.5..a1c9de56 -- Modules/FindLAPACK.cmake Modules/FindBLAS.cmake b3c42cb FindLAPACK:
[CMake] on find_package and building dependencies
Hi, yes, this is all that I can't figure out if I type the define without a type, it fails, but I can't figure out this variables type. I tried STRING and FILEPATH and even BOOL. please advice. -rhl On Thu, Dec 29, 2011 at 5:03 PM, Ryan Lewis m...@ryanlewis.net wrote: Thanks a bunch, Is there a way to hand this to cmake on the command line (i.e. an ExternalProject_Add), when I test on the command line with: cmake -DCMAKE_FIND_ROOT_PATH=... it gives me the warning that it is ignoring my define. -rhl On Thu, Dec 29, 2011 at 1:29 PM, Eric Noulard eric.noul...@gmail.com wrote: 2011/12/29 Ryan Lewis m...@ryanlewis.net: Hi, your suggestion on setting that variable before a find_package() just simply _is not_ doing what I expect. I specify my own location of libz and it _always_ finds the system wide version. Then there must be something weird, did you clean-up your build tree before testing? You may try in a fresh new pristine build tree. Would you be able to try the attached project and replace the set(CMAKE_FIND_ROOT_PATH /home/erk/TestZlib/installed) with an appropriate value for your config. You must start from a fresh new build tree. Also I cannot get the ExternalProject_Add() module to work properly. I'll try to answer that separately. Beware not to drop the CMake ML address. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CMake 2.8.7-rc2 ready for testing!
On 2011-12-29 18:34-0500 David Cole wrote: I've considered your plea, but after looking at the diffs between 2.8.5 and 2.8.7-rc2, I think we ought to keep what we have and continue moving forward with it. The commits involved are easily seen with these git commands: $ gitk v2.8.5..a1c9de56 -- Modules/FindLAPACK.cmake Modules/FindBLAS.cmake $ git log --oneline v2.8.5..a1c9de56 -- Modules/FindLAPACK.cmake Modules/FindBLAS.cmake b3c42cb FindLAPACK: List thread libs to avoid link errors (#12625) f603cf2 FindLAPACK: Correct CMAKE_FIND_LIBRARY_SUFFIXES spelling (#12624) f44f053 FindLAPACK: Fix linking to static LAPACK on Unix (#12477) 0cc8f05 FindBLAS/LAPACK fixes 145de0a FindBLAS/LAPACK fixes cfad24a fixed: search of ATLAS library for C/C++-only projects d5e6030 ACML-GPU supportede af4c58b ACML-GPU supported 91b76e2 gotoblas supported 66a4bd0 fixed: search of acml libraries I think the fixes that these commits represent outweigh the issue you've raised here late in the game. Especially since 7 of those commits are already in the 2.8.6 release. Hi Dave: I was surprised you didn't take the conservative course here since that is the CMake tradition for dealing with regressions, and the find modules for lapack/blas are dealing with a particularly complicated lapack/blas ecosystem where it is easy for these find modules to go wrong for some platforms. However, I also recognize that this is your judgement call to make, and I do hope that you are correct that the benefit of these post-2.8.5 changes is really worth the cost of the lapack/blas library inconsistency regression that was introduced by the changes. I will try to come up with a fix for the regression early in the next release cycle and run it by the lapack/blas find module maintainer, Alexey Ozeritsky. 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); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); 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 __ -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CMake 2.8.7-rc2 ready for testing!
On Thu, Dec 29, 2011 at 9:15 PM, Alan W. Irwin ir...@beluga.phys.uvic.cawrote: On 2011-12-29 18:34-0500 David Cole wrote: I've considered your plea, but after looking at the diffs between 2.8.5 and 2.8.7-rc2, I think we ought to keep what we have and continue moving forward with it. The commits involved are easily seen with these git commands: $ gitk v2.8.5..a1c9de56 -- Modules/FindLAPACK.cmake Modules/FindBLAS.cmake $ git log --oneline v2.8.5..a1c9de56 -- Modules/FindLAPACK.cmake Modules/FindBLAS.cmake b3c42cb FindLAPACK: List thread libs to avoid link errors (#12625) f603cf2 FindLAPACK: Correct CMAKE_FIND_LIBRARY_SUFFIXES spelling (#12624) f44f053 FindLAPACK: Fix linking to static LAPACK on Unix (#12477) 0cc8f05 FindBLAS/LAPACK fixes 145de0a FindBLAS/LAPACK fixes cfad24a fixed: search of ATLAS library for C/C++-only projects d5e6030 ACML-GPU supportede af4c58b ACML-GPU supported 91b76e2 gotoblas supported 66a4bd0 fixed: search of acml libraries I think the fixes that these commits represent outweigh the issue you've raised here late in the game. Especially since 7 of those commits are already in the 2.8.6 release. Hi Dave: I was surprised you didn't take the conservative course here since that is the CMake tradition for dealing with regressions, and the find modules for lapack/blas are dealing with a particularly complicated lapack/blas ecosystem where it is easy for these find modules to go wrong for some platforms. However, I also recognize that this is your judgement call to make, and I do hope that you are correct that the benefit of these post-2.8.5 changes is really worth the cost of the lapack/blas library inconsistency regression that was introduced by the changes. I will try to come up with a fix for the regression early in the next release cycle and run it by the lapack/blas find module maintainer, Alexey Ozeritsky. 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); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); 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 __ There is no conservative course here. There is a choice of whether to make CMake 2.8.7 behave the same as 2.8.6 or the same as 2.8.5. For this to be a showstopper it would have had to be reported before we tagged 2.8.6 -- since it is now already in 2.8.6, it should simply be considered a bug that we will try to address as soon as possible and get it merged into master in time for the following release. It would also be nice if this were more than simply a back-and-forth discussion between you and I. I would sure appreciate more input from other LAPACK and BLAS clients. I will take this as a personal lesson not to schedule a release of any kind the week in between Christmas and New Year's. If we stick to our schedule throughout the coming year, I'll make sure that the December release of CMake next year is well *before* Christmas. Thanks, David -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[Cmake-commits] CMake branch, master, updated. v2.8.6-445-gadd4ad1
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via add4ad1098a38c719a71fcb6e375fa50ce7be8ae (commit) from 15cebeb047d2a8be09a556898f70ed6be2d5fa16 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=add4ad1098a38c719a71fcb6e375fa50ce7be8ae commit add4ad1098a38c719a71fcb6e375fa50ce7be8ae Author: KWSys Robot kwro...@kitware.com AuthorDate: Fri Dec 30 00:05:04 2011 -0500 Commit: KWSys Robot kwro...@kitware.com CommitDate: Fri Dec 30 00:05:04 2011 -0500 KWSys Nightly Date Stamp diff --git a/Source/kwsys/kwsysDateStamp.cmake b/Source/kwsys/kwsysDateStamp.cmake index 9ee30df..2f009e0 100644 --- a/Source/kwsys/kwsysDateStamp.cmake +++ b/Source/kwsys/kwsysDateStamp.cmake @@ -18,4 +18,4 @@ SET(KWSYS_DATE_STAMP_YEAR 2011) SET(KWSYS_DATE_STAMP_MONTH 12) # KWSys version date day component. Format is DD. -SET(KWSYS_DATE_STAMP_DAY 29) +SET(KWSYS_DATE_STAMP_DAY 30) --- Summary of changes: Source/kwsys/kwsysDateStamp.cmake |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
