[cmake-developers] [CMake 0014659]: Support for MirBSD in CMake
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=14659 == Reported By:Benny Siegert Assigned To: == Project:CMake Issue ID: 14659 Category: (No Category) Reproducibility:always Severity: feature Priority: normal Status: new == Date Submitted: 2013-12-19 08:25 EST Last Modified: 2013-12-19 08:25 EST == Summary:Support for MirBSD in CMake Description: MirBSD is a derivative of OpenBSD. CMake does not build on it out of the box but with the OpenBSD platform file, it works fine. That is: $ ln Modules/Platform/OpenBSD.cmake Modules/Platform/MirBSD.cmake Then build. Could you please ship a MirBSD.cmake file that is simply a copy of the OpenBSD.cmake one? Thanks! == Issue History Date ModifiedUsername FieldChange == 2013-12-19 08:25 Benny Siegert New Issue == -- 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] documenting a CMake 'use' file
On 12/18/2013 12:13 PM, Matthew Woehlke wrote: Does this mean one cannot e.g. use the CMake extensions and/or link to topics in CMake's documentation (provided a known location of the same)? Correct. Sphinx does not support magic cross-referencing to external documents. Generating such links would require folding the document into the build process of CMake itself. Without that the links have to be spelled out like any other external hyperlinks (http://...). I have a CMake module that is going to be provided by another project (i.e. will not live in the CMake repository). It has RST documentation. I would like to be able to generate HTML from that. How would you recommend to do so? So a file that comes in a project needs to be documented with the documentation of the project. Every project has that problem with all its file types. CMake now solves it for its own files in its own source tree. Other projects will have to do their own thing. If they want to copy and re-use the infrastructure out of the CMake source tree they are free to do so but will have to maintain it themselves. Another approach is to use sed+rst2html to extract and process .rst markup from inside .cmake file comments. -Brad -- 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] define_property deprecated?
On 2013-12-18 11:52, Brad King wrote: On 12/12/2013 01:19 PM, Matthew Woehlke wrote: Loosely related: is there a way to make export() and install(EXPORT) set these properties for exported targets? Not of which I'm aware. You can have your package configuration file add them after loading the imported targets, but that would be a (centralized) workaround. For now I probably just won't support importing wrapped libraries. This would probably be a useful feature to add. I can see it being useful in any case where a project is sort-of building their own language/bindings/etc. on top of CMake (e.g. UseJava could possibly benefit also, to name at least one other). -- Matthew -- 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] FindBacktrace.cmake is slightly too chatty
Am 19.12.2013 16:28, schrieb Brad King: On 12/11/2013 02:17 AM, Vadim Zhukov wrote: It took a bit more thinking than I thought initially, sorrt. Anyway, see the last update to find_backtrace topic. Worked fine for me. I've rebased the new commit and merged the topic to 'next' for testing: FindBacktrace: Search and report only when not already found http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=9650c09b Eike, does this work as you expect now? Yes, works fine. Thx! Eike -- 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 0014660]: File tree builder is too greedy with 'sed'
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14660
==
Reported By:Joe Nardone
Assigned To:
==
Project:CMake
Issue ID: 14660
Category: CPack
Reproducibility:always
Severity: major
Priority: normal
Status: new
==
Date Submitted: 2013-12-19 12:44 EST
Last Modified: 2013-12-19 12:44 EST
==
Summary:File tree builder is too greedy with 'sed'
Description:
CPackRPM uses the following crazy `find` command to build its file list:
execute_process(COMMAND find . -type f -o -type l -o (-type d -a -not ( -name
. ${_RPM_DIRS_TO_OMIT} ) )
COMMAND sed s:.*/man.*/.*:*:
COMMAND sed s/\\.\\\(.*\\\)/\\\1\/
WORKING_DIRECTORY ${WDIR}
OUTPUT_VARIABLE CPACK_RPM_INSTALL_FILES)
However, the first `sed` is too greedy. It will match any path with the text
'man' in it. Which is fine for man pages, but for, say, a company name with
those letters in it (even if it's in the install prefix) it will match every
single item, and wildcard them. This leads to lots of files getting included
multiple times.
Steps to Reproduce:
Any package that has something like:
set(CPACK_PACKAGING_INSTALL_PREFIX /opt/manna)
should trigger it.
==
Issue History
Date ModifiedUsername FieldChange
==
2013-12-19 12:44 Joe NardoneNew Issue
==
--
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
