(0016879)
Alexandre Feblot (reporter)
2009-07-16 08:42

Maybe this feature request is connected:
http://public.kitware.com/Bug/view.php?id=8850 [^]

(0016918)
Brad King (manager)
2009-07-21 08:39

I've closed 0008850 as a duplicate of this feature request.

(0016919)
Brad King (manager)
2009-07-21 09:02

CMake does not directly drive the build, but rather generates files
for a platform's native build tool.

This issue is a limitation of the class of native build tools known as
"make". The real fix is to implement a make tool that produces
readable output.

(0016920)
Brad King (manager)
2009-07-21 09:04

The best CMake can do is work around the limitation. In CVS HEAD
CMake there are new global, directory, and target properties called
"RULE_LAUNCH_COMPILE", "RULE_LAUNCH_LINK", and "RULE_LAUNCH_CUSTOM":

  RULE_LAUNCH_COMPILE
       Specify a launcher for compile rules.

       Makefile generators prefix compiler commands with the given
       launcher command line. This is intended to allow launchers to
       intercept build problems with high granularity. Non-Makefile
       generators currently ignore this property.

  RULE_LAUNCH_CUSTOM
       Specify a launcher for custom rules.

       Makefile generators prefix custom commands with the given
       launcher command line. This is intended to allow launchers to
       intercept build problems with high granularity. Non-Makefile
       generators currently ignore this property.

  RULE_LAUNCH_LINK
       Specify a launcher for link rules.

       Makefile generators prefix link and archive commands with the
       given launcher command line. This is intended to allow
       launchers to intercept build problems with high granularity.
       Non-Makefile generators currently ignore this property.

These properties are building blocks to make use of wrapper scripts
easier. This is as far as CMake goes. CTest picks up from there, but
users can set these properties themselves too.

(0016921)
Brad King (manager)
2009-07-21 09:08
edited on: 2009-07-21 09:08

CTest takes the ball from this point in order to report granular build
results to CDash. Add this code to your project:

  set(CTEST_USE_LAUNCHERS 1)
  include(CTest)

If you already do include(CTest) and have a CTestConfig.cmake file in
the source tree you can also set CTEST_USE_LAUNCHERS in that file.
Then run

  ctest -M Experimental -T Start -T Build

at the top of the build tree. Every compilation, custom command, and linker
invocation is wrapped by a ctest launcher which reports stdout, stderr, and
other information separately. The Testing/<date>-<time> directory will
contain the results.

(0030492)
Brad King (manager)
2012-08-13 10:36

Sending issues I'm not actively working on to the backlog to await someone with time for them.

If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it:

http://www.cmake.org/mailman/listinfo/cmake [^]

It's easy to re-activate a bug here if you can find a CMake developer or contributor who has the bandwidth to take it on.

(0041420)
Kitware Robot (administrator)
2016-06-10 14:27

Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.

Issue History
Date Modified	Username	Field	Change
2008-04-09 02:26	Dieter Oberkofler	New Issue
2008-08-19 14:25	Bill Hoffman	Status	new => assigned
2008-08-19 14:25	Bill Hoffman	Assigned To	=> Bill Hoffman
2008-10-01 13:29	Bill Hoffman	Assigned To	Bill Hoffman => Brad King
2009-07-16 08:42	Alexandre Feblot	Note Added: 0016879
2009-07-21 08:35	Brad King	Relationship added	related to 0008850
2009-07-21 08:36	Brad King	Relationship replaced	has duplicate 0008850
2009-07-21 08:39	Brad King	Note Added: 0016918
2009-07-21 08:39	Brad King	Severity	minor => feature
2009-07-21 09:02	Brad King	Note Added: 0016919
2009-07-21 09:04	Brad King	Note Added: 0016920
2009-07-21 09:08	Brad King	Note Added: 0016921
2009-07-21 09:08	Brad King	Note Edited: 0016921
2012-08-13 10:36	Brad King	Status	assigned => backlog
2012-08-13 10:36	Brad King	Note Added: 0030492
2016-06-10 14:27	Kitware Robot	Note Added: 0041420
2016-06-10 14:27	Kitware Robot	Status	backlog => resolved
2016-06-10 14:27	Kitware Robot	Resolution	open => moved
2016-06-10 14:30	Kitware Robot	Status	resolved => closed

Notes
(0016879) Alexandre Feblot (reporter) 2009-07-16 08:42	Maybe this feature request is connected: http://public.kitware.com/Bug/view.php?id=8850 [^]

(0016918) Brad King (manager) 2009-07-21 08:39	I've closed 0008850 as a duplicate of this feature request.

(0016919) Brad King (manager) 2009-07-21 09:02	CMake does not directly drive the build, but rather generates files for a platform's native build tool. This issue is a limitation of the class of native build tools known as "make". The real fix is to implement a make tool that produces readable output.

(0016920) Brad King (manager) 2009-07-21 09:04	The best CMake can do is work around the limitation. In CVS HEAD CMake there are new global, directory, and target properties called "RULE_LAUNCH_COMPILE", "RULE_LAUNCH_LINK", and "RULE_LAUNCH_CUSTOM": RULE_LAUNCH_COMPILE Specify a launcher for compile rules. Makefile generators prefix compiler commands with the given launcher command line. This is intended to allow launchers to intercept build problems with high granularity. Non-Makefile generators currently ignore this property. RULE_LAUNCH_CUSTOM Specify a launcher for custom rules. Makefile generators prefix custom commands with the given launcher command line. This is intended to allow launchers to intercept build problems with high granularity. Non-Makefile generators currently ignore this property. RULE_LAUNCH_LINK Specify a launcher for link rules. Makefile generators prefix link and archive commands with the given launcher command line. This is intended to allow launchers to intercept build problems with high granularity. Non-Makefile generators currently ignore this property. These properties are building blocks to make use of wrapper scripts easier. This is as far as CMake goes. CTest picks up from there, but users can set these properties themselves too.

(0016921) Brad King (manager) 2009-07-21 09:08 edited on: 2009-07-21 09:08	CTest takes the ball from this point in order to report granular build results to CDash. Add this code to your project: set(CTEST_USE_LAUNCHERS 1) include(CTest) If you already do include(CTest) and have a CTestConfig.cmake file in the source tree you can also set CTEST_USE_LAUNCHERS in that file. Then run ctest -M Experimental -T Start -T Build at the top of the build tree. Every compilation, custom command, and linker invocation is wrapped by a ctest launcher which reports stdout, stderr, and other information separately. The Testing/<date>-<time> directory will contain the results.

(0030492) Brad King (manager) 2012-08-13 10:36	Sending issues I'm not actively working on to the backlog to await someone with time for them. If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^] It's easy to re-activate a bug here if you can find a CMake developer or contributor who has the bandwidth to take it on.

(0041420) Kitware Robot (administrator) 2016-06-10 14:27	Resolving issue as `moved`. This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.