Re: [cmake-developers] Emit link commands to file?

2016-04-09 Thread Dave Gittins 
So, it should be pretty easy to emit a json file containing those - and
maybe listing the other targets on which each target depends? That'd be
very useful.

On Sun, Apr 10, 2016 at 1:03 AM, Tamás Kenéz  wrote:

> For the "Unix Makefiles" generator, there's already a link.txt in
> /CMakeFiles/.dir
>
> Tamas
>
-- 

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] Emit link commands to file?

2016-04-09 Thread Tamás Kenéz 
For the "Unix Makefiles" generator, there's already a link.txt in
/CMakeFiles/.dir

Tamas
-- 

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 0016057]: FindBoost: No imported target when components not specified

2016-04-09 Thread Mantis Bug Tracker 

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16057 
== 
Reported By:Tatsuyuki Ishi
Assigned To:
== 
Project:CMake
Issue ID:   16057
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2016-04-09 09:58 EDT
Last Modified:  2016-04-09 09:58 EDT
== 
Summary:FindBoost: No imported target when components not
specified
Description: 
Here's an example:
=
project(...)
find_package(Boost REQUIRED)
add_executable(...)
target_link_libraries(... Boost::Boost)
*BOOM*
=

But this works:
=
find_package(Boost COMPONENTS system REQUIRED)
target_link_libraries(... Boost::Boost)
=

This is hard to use, and should be considered as bug and fixed.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-04-09 09:58 Tatsuyuki Ishi New Issue
==

-- 

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] Emit link commands to file?

2016-04-09 Thread Dave Gittins 
Enabling CMAKE_EXPORT_COMPILE_COMMANDS causes CMake to emit
compile_commands.json, to be picked up by llvm tools or other custom stuff.
This is very useful.

Can we also have a link_commands.json that records the link commands that
produce each target? That would allow a whole new set of validation to be
performed on the structure of the build and the linking arrangements.

I am trying to perform some of those validations on some large CMake
projects but it's hard at the moment - I either have to try to explore the
situation within CMake, or parse the generated build files, or parse the
verbose build output - none of which is working very well!

I am willing to try implementing this feature myself, if it's considered
potentially useful and doesn't overlap with ongoing work or something.

Any thoughts?

Dave
-- 

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] [Patch] Improve documentation of FindMPI

2016-04-09 Thread Christoph Grüninger 
Dear CMake developers,
please find attached patch to improve the formatting of the FindMPI
documentation.

Bye
Christoph

-- 
My new computer came with Windows 7.
Windows 7 is much more user-friendly than Windows Vista.
I don't like that. [Sheldon, S03E13]
>From 10c61ef2dda8ce5bab8162e15d9dfbf4a614fd91 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Christoph=20Gr=C3=BCninger?= 
Date: Sat, 9 Apr 2016 10:05:27 +0200
Subject: [PATCH] Help: improve formating of FindMPI

---
 Modules/FindMPI.cmake | 27 +++
 1 file changed, 15 insertions(+), 12 deletions(-)

diff --git a/Modules/FindMPI.cmake b/Modules/FindMPI.cmake
index 48adf3c..501ed91 100644
--- a/Modules/FindMPI.cmake
+++ b/Modules/FindMPI.cmake
@@ -11,7 +11,8 @@
 # of them have somewhat different include paths, libraries to link
 # against, etc., and this module tries to smooth out those differences.
 #
-# === Variables ===
+# Variables
+# =
 #
 # This module will set the following variables per language in your
 # project, where  is one of C, CXX, or Fortran:
@@ -37,11 +38,12 @@
 #   before the executable to run.
 #MPIEXEC_POSTFLAGS  Flags to pass to MPIEXEC after other flags
 #
-# === Usage ===
+# Usage
+# =
 #
 # To use this module, simply call FindMPI from a CMakeLists.txt file, or
-# run find_package(MPI), then run CMake.  If you are happy with the
-# auto- detected configuration for your language, then you're done.  If
+# run ``find_package(MPI)``, then run CMake.  If you are happy with the
+# auto-detected configuration for your language, then you're done.  If
 # not, you have two options:
 #
 # ::
@@ -55,24 +57,25 @@
 #   listed above, but these two are required.  This will circumvent
 #   autodetection entirely.
 #
-# When configuration is successful, MPI__COMPILER will be set to
-# the compiler wrapper for , if it was found.  MPI__FOUND
+# When configuration is successful, ``MPI__COMPILER`` will be set to
+# the compiler wrapper for , if it was found.  ``MPI__FOUND``
 # and other variables above will be set if any MPI implementation was
 # found for , regardless of whether a compiler was found.
 #
-# When using MPIEXEC to execute MPI applications, you should typically
-# use all of the MPIEXEC flags as follows:
+# When using ``MPIEXEC`` to execute MPI applications, you should typically
+# use all of the ``MPIEXEC`` flags as follows:
 #
 # ::
 #
 #${MPIEXEC} ${MPIEXEC_NUMPROC_FLAG} PROCS
 #  ${MPIEXEC_PREFLAGS} EXECUTABLE ${MPIEXEC_POSTFLAGS} ARGS
 #
-# where PROCS is the number of processors on which to execute the
-# program, EXECUTABLE is the MPI program, and ARGS are the arguments to
+# where ``PROCS`` is the number of processors on which to execute the
+# program, ``EXECUTABLE`` is the MPI program, and ``ARGS`` are the arguments to
 # pass to the MPI program.
 #
-# === Backward Compatibility ===
+# Backward Compatibility
+# ==
 #
 # For backward compatibility with older versions of FindMPI, these
 # variables are set, but deprecated:
@@ -83,7 +86,7 @@
 #MPI_COMPILE_FLAGS   MPI_INCLUDE_PATHMPI_EXTRA_LIBRARY
 #MPI_LINK_FLAGS  MPI_LIBRARIES
 #
-# In new projects, please use the MPI__XXX equivalents.
+# In new projects, please use the ``MPI__XXX`` equivalents.
 
 #=
 # Copyright 2001-2011 Kitware, Inc.
-- 
2.6.6

-- 

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