MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012275CMakeCMakepublic2011-06-15 07:072016-06-10 14:31
ReporterJohan Björk 
Assigned ToKitware Robot 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product VersionCMake 2.8.4 
Target VersionFixed in Version 
Summary0012275: XCode generator does not remove generated files with the 'clean' target.
DescriptionGenerated files don't get removed in the clean target when using the XCode generator.

Steps To ReproduceUse following CMakeLists.txt


PROJECT(foo)

 ADD_CUSTOM_COMMAND(
   OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/apa.cpp
   COMMAND touch ${CMAKE_CURRENT_BINARY_DIR}/apa.cpp
)


ADD_CUSTOM_TARGET(foo ALL
    DEPENDS ${CMAKE_CURRENT_BINARY_DIR}/apa.cpp)

---
run
cmake -G Xcode ../
cmake --build . --config Release

cmake --build . --config Release --target clean
Observe that apa.cpp is still present in the build directory.

The same with the Makefile generator properly cleans up the generated file.

Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-06-15 07:07Johan BjörkNew Issue
2011-08-18 15:35Johan BjörkNote Added: 0027242
2012-08-11 11:38David ColeStatusnew => backlog
2012-08-11 11:38David ColeNote Added: 0030294
2016-06-10 14:28Kitware RobotNote Added: 0041850
2016-06-10 14:28Kitware RobotStatusbacklog => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:28Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0027242)
Johan Björk   
2011-08-18 15:35   
Looked a bit at this, I think we'll have to add a PBXLegacy target as a dependency for the targets with custom commands (that has output files) :(

More info can be found here:

http://yeahrightkeller.com/2009/run-script-while-cleaning-in-xcode/ [^]
(0030294)
David Cole   
2012-08-11 11:38   
Sending old, never assigned issues to the backlog.

(The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...)

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 who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.
(0041850)
Kitware Robot   
2016-06-10 14:28   
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.