MantisBT - CMake
View Issue Details
0012430CMakeCMakepublic2011-08-30 01:482012-03-06 08:37
Jean-Christophe Fillion-Robin 
David Cole 
normalminoralways
closedno change required 
Windows7
 
CMake 2.8.7 
0012430: ExternalProject - VisualStudio - ExternalProject_Add_Step requires the COMMAND argument
Generator: Visual Studio 9 2008 / Visual Studio 9 2008 Win64
CMake version: 2.8.2 -> 2.8.6rc1

If you comment line 28 of the enclosed CMakeLists.txt, the build step of the associated project won't be systematically executed whereas it should.
No tags attached.
tgz ExternalProject-AddStep-COMMAND-required-on-VS9.tgz (648) 2011-08-30 01:48
https://public.kitware.com/Bug/file/4036/ExternalProject-AddStep-COMMAND-required-on-VS9.tgz
Issue History
2011-08-30 01:48Jean-Christophe Fillion-RobinNew Issue
2011-08-30 01:48Jean-Christophe Fillion-RobinFile Added: ExternalProject-AddStep-COMMAND-required-on-VS9.tgz
2011-08-31 13:32David ColeAssigned To => David Cole
2011-08-31 13:32David ColeStatusnew => assigned
2011-08-31 13:36David ColeNote Added: 0027314
2011-10-25 23:14David ColeNote Added: 0027649
2011-10-25 23:14David ColeStatusassigned => resolved
2011-10-25 23:14David ColeFixed in Version => CMake 2.8.7
2011-10-25 23:14David ColeResolutionopen => no change required
2012-03-06 08:37David ColeNote Added: 0028834
2012-03-06 08:37David ColeStatusresolved => closed

Notes
(0027314)
David Cole   
2011-08-31 13:36   
So, do you want the requirement for using "COMMAND" documented or eliminated?

The intent of the add step is to actually have a COMMAND. You're using it simply as an "ALWAYS" injection mechanism to make "build" an effectively ALWAYS step.
(0027649)
David Cole   
2011-10-25 23:14   
Please use the COMMAND for a custom step. You can always make it a no-op command if there's really no command associated with the "step"...
(0028834)
David Cole   
2012-03-06 08:37   
Closing resolved issues that have not been updated in more than 4 months.