Re: [cmake-developers] cmake-3.3.0-Linux-x86_64.tar.gz on download page is not gzipped
thank you for the good catch and for fixing this! now the download behaves as expected on my Chrome version. thank you again and keep it up! radovan On Mon, Aug 3, 2015 at 8:05 PM Brad King brad.k...@kitware.com wrote: On 07/31/2015 09:54 AM, Nils Gladitz wrote: The HTTP response for cmake-3.3.0.tar.gz does contain: Content-Encoding: x-gzip Thanks for pointing this out. Which I think does tell clients that they should decompress to get the actual content which is declared to be of Content-Type:application/x-gzip; this is I think incorrect unless the HTTP server compresses the .tar.gz once more with gzip before delivery. Our admins have fixed the configuration on the server so that there is no Content-Encoding header for .Z and .gz files anymore. I think that configuration was there by mistake. -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] cmake-3.3.0-Linux-x86_64.tar.gz on download page is not gzipped
thanks Brad! interesting. sorry for the noise. best wishes, radovan On Fri, Jul 31, 2015 at 3:09 PM Brad King brad.k...@kitware.com wrote: On 07/31/2015 07:14 AM, Radovan Bast wrote: the cmake-3.3.0-Linux-x86_64.tar.gz on http://www.cmake.org/download/ is not gzipped. Yes, it is. From a shell on the hosting server: $ file cmake-3.3.0-Linux-x86_64.tar.gz cmake-3.3.0-Linux-x86_64.tar.gz: gzip compressed data, ... $ shasum -a 256 cmake-3.3.0-Linux-x86_64.tar.gz 25d1f60cec20c89d7a8d6aa608af8766bd2f7de978ae5f2ae1e67641bdd1b8ed cmake-3.3.0-Linux-x86_64.tar.gz I think some browsers or other download tools may automatically gunzip files during download. -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] cmake-3.3.0-Linux-x86_64.tar.gz on download page is not gzipped
Indeed a Chrome version that I have installed today does that to my surprise. Auto-unpacks during download but keeps the suffix. I would like to ask why but this is not the right list :-) Thanks again for the clarification! radovan On Fri, Jul 31, 2015 at 3:11 PM Radovan Bast radovan.b...@gmail.com wrote: thanks Brad! interesting. sorry for the noise. best wishes, radovan On Fri, Jul 31, 2015 at 3:09 PM Brad King brad.k...@kitware.com wrote: On 07/31/2015 07:14 AM, Radovan Bast wrote: the cmake-3.3.0-Linux-x86_64.tar.gz on http://www.cmake.org/download/ is not gzipped. Yes, it is. From a shell on the hosting server: $ file cmake-3.3.0-Linux-x86_64.tar.gz cmake-3.3.0-Linux-x86_64.tar.gz: gzip compressed data, ... $ shasum -a 256 cmake-3.3.0-Linux-x86_64.tar.gz 25d1f60cec20c89d7a8d6aa608af8766bd2f7de978ae5f2ae1e67641bdd1b8ed cmake-3.3.0-Linux-x86_64.tar.gz I think some browsers or other download tools may automatically gunzip files during download. -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
[cmake-developers] cmake-3.3.0-Linux-x86_64.tar.gz on download page is not gzipped
dear all, the cmake-3.3.0-Linux-x86_64.tar.gz on http://www.cmake.org/download/ is not gzipped. this confused me a bit since tar xvzf complained. of course it can be extracted still but i think it would be good to replace it by the compressed one. thank you and best wishes, radovan -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Fortran module dependencies and preprocessing in CMake 3.3.0-rc3
dear Brad, SOMEDEF is defined at compile time. Attached is a tarball that contains the CMakeLists.txt which defines SOMEDEF, a main.F90 and a mymodule.F90 which contains the module which is not built prior to building main.F90. In principle the problem can be reproduced like this: ``` tar xvzf example.tar.gz cd example/ mkdir build cd build/ cmake .. make ``` Thank you for looking into this! Best wishes, radovan On Mon, Jul 6, 2015 at 3:02 PM Brad King brad.k...@kitware.com wrote: On 07/02/2015 06:25 PM, Radovan Bast wrote: I can consistently reproduce it locally on 3 different machines (Ubuntu 14.04 and Arch derivative; gfortran 4.8.4 and 5.1.0). I have Git bisected the history and this is the commit that broke this example on my machines: https://github.com/Kitware/CMake/commit/0b945ea9a6a38d1b3ee27cc32afb4268bd571600 Thanks for bisecting! Can you see something possibly related in there? That change may have accidentally affected the preprocessor definitions sent to the Fortran compiler. The error message you're seeing is actually coming from the compiler trying to use the module, so SOMEDEF must be getting defined. However, without seeing your CMake code I cannot determine how. Can you provide a minimal source tarball that exhibits the problem? Thanks, -Brad example.tar.gz Description: application/gzip -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Fortran module dependencies and preprocessing in CMake 3.3.0-rc3
dear Brad, thanks a lot! This is very much appreciated. Best wishes, radovan On Mon, Jul 6, 2015 at 4:41 PM Brad King brad.k...@kitware.com wrote: On 07/06/2015 09:13 AM, Radovan Bast wrote: SOMEDEF is defined at compile time. Attached is a tarball that contains the CMakeLists.txt which defines SOMEDEF, a main.F90 and a mymodule.F90 which contains the module which is not built prior to building main.F90. Thanks. I've drafted a fix and a test case: Fortran: Fix passing of preprocessor definitions to dependency scanner http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0a203db5 If it passes nightly testing I'll merge it to 'release' for 3.3. Thanks, -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
[cmake-developers] Fortran module dependencies and preprocessing in CMake 3.3.0-rc3
dear CMake developers, We have observed a changed and surprising behavior in CMake 3.3.0-rc3 with Fortran module dependency scanning and preprocessing compared to earlier CMake versions (for instance 3.2.3). I have checked open bugs and email list archives but could not find this mentioned. To give an example the following Fortran source fails to compile: program example #ifdef SOMEDEF use mymodule #endif call hello() end program with: main.F90:3:7: use mymodule 1 Fatal Error: Can't open module file ‘mymodule.mod’ for reading at (1): No such file or directory It seems that Fortran dependencies are scanned prior to pre-processing. This seems different compared to 3.2.3 (and earlier versions). Not sure this is a bug or a feature. All relevant files (CMakeLists.txt, main.F90, mymodule.F90) for a complete minimal example are attached. I can also submit this directly to http://www.cmake.org/Bug/ in case this is not a feature. Thank you and best wishes, radovan cmake_minimum_required(VERSION 2.8 FATAL_ERROR) project(example) enable_language(Fortran) add_definitions(-DSOMEDEF) add_executable(example.x main.F90 mymodule.F90) #ifdef SOMEDEF module mymodule contains subroutine hello() print *, 'hello' end subroutine end module #else subroutine empty() end subroutine #endif program example #ifdef SOMEDEF use mymodule #endif call hello() end program -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Fortran module dependencies and preprocessing in CMake 3.3.0-rc3
dear Brad, thanks for testing it on your side and also for the suggestions! I can consistently reproduce it locally on 3 different machines (Ubuntu 14.04 and Arch derivative; gfortran 4.8.4 and 5.1.0). I have Git bisected the history and this is the commit that broke this example on my machines: https://github.com/Kitware/CMake/commit/0b945ea9a6a38d1b3ee27cc32afb4268bd571600 Can you see something possibly related in there? thank you best wishes, radovan On Thu, Jul 2, 2015 at 3:30 PM Brad King brad.k...@kitware.com wrote: On 07/02/2015 04:14 AM, Radovan Bast wrote: We have observed a changed and surprising behavior in CMake 3.3.0-rc3 with Fortran module dependency scanning and preprocessing compared to earlier CMake versions (for instance 3.2.3). I don't recall any changes related to this since 3.2. I also cannot reproduce the problem with the example you provided. It seems that Fortran dependencies are scanned prior to pre-processing. CMake does its own approximate preprocessing for dependency scanning. This hasn't changed in a long time. Can you please provide a more complete example to reproduce this? Or, if you can consistently reproduce it locally please try bisecting our Git history between 3.2 and 3.3 to see if you can find the commit that introduced the problem. Thanks, -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [CMake] support for .f03/.F03 suffix (Fortran 2003)
thank you Zaak! you are right, after some more reading on this issue i should stick to .f90 as you suggest. thank you for the clarification. best regards, radovan On Wed, Jul 31, 2013 at 10:44 PM, Zaak Beekman zbeek...@gmail.com wrote: dear all, it seems that CMake currently does not support .f03/.F03 suffix for Fortran 2003 files. is there a way for me to tell CMake to treat these files as it would treat files ending with .f90 or .f95. i can then assign special flags to them via source file properties. thank you in advance best regards, radovan Radovan, I'm curious why you want to use .f03 or .f08 extensions. Some compilers--like Intel's--explicitly forbid this. For portability I would recommend sticking with the .f90 suffix. I suspect you can adjust the following variable to implement a work around, although I am a CMake newbie and have not tried it myself: CMAKE_Fortran_SOURCE_FILE_EXTENSIONS [ http://www.cmake.org/cmake/help/v2.8.8/cmake.html#variable:CMAKE_LANG_SOURCE_FILE_EXTENSIONS ] -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] support for .f03/.F03 suffix (Fortran 2003)
dear all, it seems that CMake currently does not support .f03/.F03 suffix for Fortran 2003 files. is there a way for me to tell CMake to treat these files as it would treat files ending with .f90 or .f95. i can then assign special flags to them via source file properties. thank you in advance best regards, radovan -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CMake Download Version for Linux x86-64 platform
hi, what i did very often was to extract the Linux i386 binary distribution on a x86-64 platfrom and i never had problems with it. good luck, radovan On Tue, Jun 11, 2013 at 5:26 PM, Alain Leblanc aal...@gmail.com wrote: Which distribution? Probably one of opensuse, fedora, ubuntu, mint, arch, ... On some systems typing cat /proc/version or uname -a will give you this information 2013/6/11 setareh S setareh.s1...@gmail.com Thanks Alain. I checked my system and I get something like: GNU/Linux (Kernel: Linux, Kernel release: 2.6.32.12-0.7)on a x84-64 machine with GNOME gnome-panel 2.28.0 desktop. Any ideas? On Tue, Jun 11, 2013 at 4:53 PM, Alain Leblanc aal...@gmail.com wrote: Most linux distros will provide a cmake package. I don't know which platform you're using, but on opensuse, for instance, you only need to type sudo zypper install cmake on ubuntu, it would be ( I think) sudo apt-get install cmake and so on. a 2013/6/11 setareh S setareh.s1...@gmail.com Dear CMake users, what version of CMake binary distribution file from the CMake download page should I use to install CMake on a Linux x86-64 platfrom machine? I don't see any binary distribution for x86-64 there. Thank you. Setareh -- 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 -- 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] CTest: make Experimental/Nightly on N procs with -jN
dear all, it is possible to run make test in parallel using several processors using: $ ARGS=-j4 make test this does not seem to be the case for Experimental/Nightly. inspecting the targets in the Makefiles i can see ARGS in test but not in Experimental/Nightly. do you know of a way/workaround to run (sequential) Experimental/Nightly tests on N procs in parallel? thank you and best regards, radovan -- 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] CTest: make Experimental/Nightly on N procs with -jN
thanks a lot David! this works very nicely. best regards, radovan On Fri, May 31, 2013 at 4:34 PM, David Cole dlrd...@aol.com wrote: this does not seem to be the case for Experimental/Nightly. inspecting the targets in the Makefiles i can see ARGS in test but not in Experimental/Nightly. do you know of a way/workaround to run (sequential) Experimental/Nightly tests on N procs in parallel? Just run it directly instead of going through make: ctest -D Experimental -j4 HTH, 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
Re: [CMake] is it possible to download CMake modules at configure time?
dear Jean-Christophe, indeed the approach you demostrated works for me! this is exactly what i needed. thank you again! (i am sorry for coming back to you so late; was too busy with other things) best regards, radovan On Sat, 13 Apr 2013 12:24:02 +0200, Jean-Christophe Fillion-Robin jchris.filli...@kitware.com wrote: Hi Radovan, Did you manage to make use and/or generalize the code I pointed you? Thanks Jc -- Sent from my mobile device On Apr 6, 2013 10:29 AM, radovan bast rado...@bast.fr wrote: dear Jean-Christophe, wonderful! thank you very much. i will test it out. best regards, radovan On Fri, 05 Apr 2013 18:13:52 +0200, Jean-Christophe Fillion-Robin jchris.filli...@kitware.com wrote: Hi Radovan, This is possible. You could look at the approach we consider in CTK. See https://github.com/commontk/**CTK/compare/** 00694c9f8a0da6ee28fb079902e6a8**c3ec428058...** 891aa5443b110cc7e6aa0ec1339aad**4b2c83ef9dhttps://github.com/commontk/CTK/compare/00694c9f8a0da6ee28fb079902e6a8c3ec428058...891aa5443b110cc7e6aa0ec1339aad4b2c83ef9d Hth Jc On Fri, Apr 5, 2013 at 12:03 PM, radovan bast radovan.b...@irsamc.ups-tlse.**fr radovan.b...@irsamc.ups-tlse.fr wrote: dear CMake developers and users, first of all, a big thanks for the CMake developers for a great product! we like CMake a lot. we are extensively using CMake external project support in combination with Git submodules in a number of larger projects and that works nicely. my question is: could i do something similar with CMake modules? is it possible to start with a minimal core CMakeLists.txt which would fetch other CMake modules from an external public (Git) repository and use them to configure the project? the motivation for this is that we have several projects with rather complex CMake infrastructures. the projects are independent, live on different repositories, but the CMake infrastructures are to a large extent overlapping. currently we synchronize the CMake code between these projects manually but this is not great and there is the risk that the codes will diverge, that wheels will be reinvented, and that improvements are not communicated between the projects. this could be avoided if the CMake code was not explicitly present but fetched from a repository which would also enforce (or encourage) communicating all improvements to the same place. everything that is generic and not project specific would go into that external repo, only project specific things would be kept in the minimal core CMakeLists.txt. i will appreciate any pointers and suggestions on how i could implement such a scheme. thanks and best regards, radovan -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/** opensource/opensource.htmlhtt**p://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 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 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] is it possible to download CMake modules at configure time?
dear Jean-Christophe, absolutely. it will take a bit of time until we finetune things but the plan is to have and share an open source repository (probably on github) that will provide generic plug-n-play CMake infrastructure for projects that require Fortran, C, and C++, as well as MPI/OpenMP, BLAS, and LAPACK. the focus is on scientific computing but i will try to keep things general and generic also for other projects. best greetings, radovan On Fri, 19 Apr 2013 18:45:04 +0200, Jean-Christophe Fillion-Robin jchris.filli...@kitware.com wrote: Hi Radovan, That is good news :) Do you think you could share the CMake code you ended up created. May be could generalize the solution to create a re-usable module. Thanks Jc On Fri, Apr 19, 2013 at 12:23 PM, radovan bast radovan.b...@irsamc.ups-tlse.fr wrote: dear Jean-Christophe, indeed the approach you demostrated works for me! this is exactly what i needed. thank you again! (i am sorry for coming back to you so late; was too busy with other things) best regards, radovan On Sat, 13 Apr 2013 12:24:02 +0200, Jean-Christophe Fillion-Robin jchris.filli...@kitware.com wrote: Hi Radovan, Did you manage to make use and/or generalize the code I pointed you? Thanks Jc -- Sent from my mobile device On Apr 6, 2013 10:29 AM, radovan bast rado...@bast.fr wrote: dear Jean-Christophe, wonderful! thank you very much. i will test it out. best regards, radovan On Fri, 05 Apr 2013 18:13:52 +0200, Jean-Christophe Fillion-Robin jchris.filli...@kitware.com wrote: Hi Radovan, This is possible. You could look at the approach we consider in CTK. See https://github.com/commontk/CTK/compare/**https://github.com/commontk/**CTK/compare/** 00694c9f8a0da6ee28fb079902e6a8c3ec428058...** 891aa5443b110cc7e6aa0ec1339aad4b2c83ef9dhttps://github.** com/commontk/CTK/compare/**00694c9f8a0da6ee28fb079902e6a8** c3ec428058...**891aa5443b110cc7e6aa0ec1339aad**4b2c83ef9dhttps://github.com/commontk/CTK/compare/00694c9f8a0da6ee28fb079902e6a8c3ec428058...891aa5443b110cc7e6aa0ec1339aad4b2c83ef9d Hth Jc On Fri, Apr 5, 2013 at 12:03 PM, radovan bast radovan.b...@irsamc.ups-tlse.fr radovan.b...@irsamc.ups-tlse.**frradovan.b...@irsamc.ups-tlse.fr wrote: dear CMake developers and users, first of all, a big thanks for the CMake developers for a great product! we like CMake a lot. we are extensively using CMake external project support in combination with Git submodules in a number of larger projects and that works nicely. my question is: could i do something similar with CMake modules? is it possible to start with a minimal core CMakeLists.txt which would fetch other CMake modules from an external public (Git) repository and use them to configure the project? the motivation for this is that we have several projects with rather complex CMake infrastructures. the projects are independent, live on different repositories, but the CMake infrastructures are to a large extent overlapping. currently we synchronize the CMake code between these projects manually but this is not great and there is the risk that the codes will diverge, that wheels will be reinvented, and that improvements are not communicated between the projects. this could be avoided if the CMake code was not explicitly present but fetched from a repository which would also enforce (or encourage) communicating all improvements to the same place. everything that is generic and not project specific would go into that external repo, only project specific things would be kept in the minimal core CMakeLists.txt. i will appreciate any pointers and suggestions on how i could implement such a scheme. thanks and best regards, radovan -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/** opensource/opensource.html**htt**p://www.kitware.com/** opensource/opensource.htmlhtt**p://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 http://www.cmake.**org/Wiki/**CMake_FAQhttp://www.cmake.org/Wiki/**CMake_FAQ http://www.cmake.**org/Wiki/**CMake_FAQhttp://www.cmake.** org/Wiki/CMake_FAQ http://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 http://www.**cmake.org/mailman/**listinfo/**cmakehttp://www.cmake.org/mailman/**listinfo/cmake http://www.**cmake.org/**mailman/listinfo/**cmakehttp://cmake.org/mailman/listinfo/**cmake 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] is it possible to download CMake modules at configure time?
dear CMake developers and users, first of all, a big thanks for the CMake developers for a great product! we like CMake a lot. we are extensively using CMake external project support in combination with Git submodules in a number of larger projects and that works nicely. my question is: could i do something similar with CMake modules? is it possible to start with a minimal core CMakeLists.txt which would fetch other CMake modules from an external public (Git) repository and use them to configure the project? the motivation for this is that we have several projects with rather complex CMake infrastructures. the projects are independent, live on different repositories, but the CMake infrastructures are to a large extent overlapping. currently we synchronize the CMake code between these projects manually but this is not great and there is the risk that the codes will diverge, that wheels will be reinvented, and that improvements are not communicated between the projects. this could be avoided if the CMake code was not explicitly present but fetched from a repository which would also enforce (or encourage) communicating all improvements to the same place. everything that is generic and not project specific would go into that external repo, only project specific things would be kept in the minimal core CMakeLists.txt. i will appreciate any pointers and suggestions on how i could implement such a scheme. thanks and best regards, radovan -- 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
