Re: [cmake-developers] cmake --help-concept
Brad King wrote: On 08/28/2013 03:28 PM, Stephen Kelly wrote: We should add these concept sections to the docs and we can add 'See the documentation of the generator_expression concept' where it makes sense. We should not change or extend the markup or make adding these concept sections dependent on choosing and implementing a new markup for docs. The --help-concept proposal is for a specific new section rather than general infrastructure for adding sections. It can be one man page that has an item for each concept, just like the command help has an item for each command. This can be done independent of other changes discussed in the thread Alex linked. I've pushed the concept-help branch to next for review, along with one documentation item on policies. Once the details are worked out and merged, I can write some more, and Alex may want to too. Thanks, Steve. -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] cmake --help-concept
On Saturday 14 September 2013, Stephen Kelly wrote: Brad King wrote: On 08/28/2013 03:28 PM, Stephen Kelly wrote: We should add these concept sections to the docs and we can add 'See the documentation of the generator_expression concept' where it makes sense. We should not change or extend the markup or make adding these concept sections dependent on choosing and implementing a new markup for docs. The --help-concept proposal is for a specific new section rather than general infrastructure for adding sections. It can be one man page that has an item for each concept, just like the command help has an item for each command. This can be done independent of other changes discussed in the thread Alex linked. I've pushed the concept-help branch to next for review, along with one documentation item on policies. Once the details are worked out and merged, I can write some more, and Alex may want to too. Would e.g. the list of supported languages or toolchains be a candidate for that concepts section ? Or should the languages be documented in the enable_language() documentation ? Alex -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] (naming-)convention for ALIAS and INTERFACE targets
On Friday 13 September 2013, Daniel Pfeifer wrote: Hi Steve and all, we restarted the CMake-ification of molularized Boost with modern CMake features here: https://github.com/boost-cmake/boost-cmake We want to be able to build all Boost libraries together, but also each library on its own. Am I correct that in both cases we use the :: name in tll()? The :: target name is an ALIAS in the first use case and an imported INTERFACE in the second, right? I assume that, for the INTERFACE case, the interfaces need to be imported with find_package(). How can we make sure that calling find_package() does not get in the way when Boost is built as a whole? I think you have to put an if(built_standalone ?) around it. or check whether some target is already existing, something like if(NOT TARGET SomeBoostTarget). Boost also provides some tools for building documentation. To simplify using these tools with CMake, we want to make them provide also some CMake modules. Note that we don't want to put these modules in a common location, but let each Boost tool bring its own module. Since those modules will be used by Boost itself, they should be usable from both the install dir and the source dir. What would be better? 1) Let Boostbook provide a module UseBoostbook.cmake 2) Put all Boostbook related functions into FindBoostbook.cmake If Boostbook installs a Config.cmake file (that's the case, right ?), I would make the Boostbook functions part of Boostbook, i.e. include() the file containing the functions/macros in the Config.cmake file. Alex -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] cmake --help-concept
Alexander Neundorf wrote: On Saturday 14 September 2013, Stephen Kelly wrote: Brad King wrote: On 08/28/2013 03:28 PM, Stephen Kelly wrote: We should add these concept sections to the docs and we can add 'See the documentation of the generator_expression concept' where it makes sense. We should not change or extend the markup or make adding these concept sections dependent on choosing and implementing a new markup for docs. The --help-concept proposal is for a specific new section rather than general infrastructure for adding sections. It can be one man page that has an item for each concept, just like the command help has an item for each command. This can be done independent of other changes discussed in the thread Alex linked. I've pushed the concept-help branch to next for review, along with one documentation item on policies. Once the details are worked out and merged, I can write some more, and Alex may want to too. Would e.g. the list of supported languages or toolchains be a candidate for that concepts section ? Or should the languages be documented in the enable_language() documentation ? I'd say that if there's a language concept section, it would say that the project command can be used to enable languages, and that it enables C and CXX by default. It would also say that enable_language can be used to enable languages. It would also list the language specfic variables that can be set by the user. If 3rd party language support is a supported use-case of cmake (I'm not sure), it would describe how to add support for a language. It could also list the languages built-in to CMake, but it would be more than just a list. It should be a starting point to other commands and variables relevant to language support in CMake. Thanks, Steve. -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] CMake libarchive bug? (not new...)
CMake 2.8.12-rc3 cannot extract these .tar.gz files via cmake -E tar xzf: https://github.com/zeromq/zeromq3-x/archive/v3.2.2.tar.gz https://github.com/zeromq/zeromq3-x/archive/v3.2.3.tar.gz https://github.com/zeromq/zeromq3-x/archive/master.tar.gz But this is not a recent (if at all) regression, 2.8.10 and 2.8.11 also fail to extract them... There's also an error if trying to extract the equivalent .zip files (replace .tar.gz with .zip in the URLs...) It is always on the same file, doc/zmq_epgm.txt, with output like this: -- extracting... [tar xfz] CMake Error: Problem with archive_write_header(): Can't create '\\?\C:...\src\ex-download-zeromq1234\zeromq3-x-3.2.3\doc\zmq_epgm.txt' CMake Error: Current file: zeromq3-x-3.2.3/doc/zmq_epgm.txt CMake Error: Problem extracting tar: C:/.../Downloads/zeromq3-x-v3.2.3.tar.gz -- extracting... [error clean up] CMake Error at C:/.../download-zeromq-prefix/src/download-zeromq-stamp/extract-download- zeromq.cmake:33 (message): error: extract of 'C:/.../Downloads/zeromq3-x-v3.2.3.tar.gz' failed CMake bug? Libarchive bug? Maybe fixed already upstream? One more tidbit: 7-zip *can* extract the archives just fine, so I don't think there's anything unrecoverably wrong with the archive files themselves. Anybody have a quick fix or a workaround I can use? (I'm not a fan of using 7-zip for the extraction, or of using git snapped to a tag: I'm trying to make a super build work with just cmake -E and .tar.gz files. If I must, I'll simply create a new tar.gz without the file that's making it choke, and use that... I'd really prefer to use the official one from github, though. So I don't have to host a custom one anywhere...) Thanks, David C. -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] CMake libarchive bug? (not new...)
2013/9/14 David Cole dlrd...@aol.com: CMake 2.8.12-rc3 cannot extract these .tar.gz files via cmake -E tar xzf: https://github.com/zeromq/zeromq3-x/archive/v3.2.2.tar.gz https://github.com/zeromq/zeromq3-x/archive/v3.2.3.tar.gz https://github.com/zeromq/zeromq3-x/archive/master.tar.gz But this is not a recent (if at all) regression, 2.8.10 and 2.8.11 also fail to extract them... There's also an error if trying to extract the equivalent .zip files (replace .tar.gz with .zip in the URLs...) It is always on the same file, doc/zmq_epgm.txt, with output like this: This file is a symbolic link: lrwxrwxrwx root/root 0 2013-08-24 08:09 zeromq3-x-master/doc/zmq_epgm.txt - zmq_pgm.txt I don't have any trouble using cmake version 2.8.11.20130914-g396df-dirty (git master) Q1) Do you do the extraction on Windows or Linux? If you are on Windows then this is the well-know trouble of unsupported lilbarchive feature on Windows. Dig the CMake ML and/or libarchive tracker and you'll find out. Q2) Is your CMake compiled with system libarchive or the one thar comes with CMake ? -- extracting... [tar xfz] CMake Error: Problem with archive_write_header(): Can't create '\\?\C:...\src\ex-download-zeromq1234\zeromq3-x-3.2.3\doc\zmq_epgm.txt' CMake Error: Current file: zeromq3-x-3.2.3/doc/zmq_epgm.txt CMake Error: Problem extracting tar: C:/.../Downloads/zeromq3-x-v3.2.3.tar.gz -- extracting... [error clean up] CMake Error at C:/.../download-zeromq-prefix/src/download-zeromq-stamp/extract-download- zeromq.cmake:33 (message): error: extract of 'C:/.../Downloads/zeromq3-x-v3.2.3.tar.gz' failed CMake bug? Libarchive bug? Maybe fixed already upstream? One more tidbit: 7-zip *can* extract the archives just fine, so I don't think there's anything unrecoverably wrong with the archive files themselves. Anybody have a quick fix or a workaround I can use? (I'm not a fan of using 7-zip for the extraction, or of using git snapped to a tag: I'm trying to make a super build work with just cmake -E and .tar.gz files. If I must, I'll simply create a new tar.gz without the file that's making it choke, and use that... I'd really prefer to use the official one from github, though. So I don't have to host a custom one anywhere...) Thanks, David C. -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers -- Erk L'élection n'est pas la démocratie -- http://www.le-message.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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] CMake libarchive bug? (not new...)
Ah, of course. A symlink. Thank you. Yes, I'm on Windows and using the pre-built binaries of CMake from cmake.org. It's annoying that cross-platform projects actually have symlinks in their source trees. Thanks, D -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
