View Issue Details [ Jump to Notes ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0015725CMakeCMakepublic2015-09-03 12:112016-02-01 09:10
ReporterGregory Kramida 
Assigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
StatusclosedResolutionwon't fix 
PlatformOSOS Version
Product VersionCMake 3.3.1 
Target VersionFixed in Version 
Summary0015725: post generate action
DescriptionIt would be great if users had the ability to schedule processes after the generation step.

There are many ways, i.e. adding another command, but I guess the easiest way to achieve that would be by extending the execute_process command with something like a SCHEDULE_AFTER_GENERATION flag.
Additional InformationSee http://www.cmake.org/pipermail/cmake/2010-May/037151.html [^]
See comments in answer here http://stackoverflow.com/questions/7091447/run-command-after-generation-step-in-cmake [^]
TagsNo tags attached.
Attached Files

 Relationships

  Notes
(0039375)
Brad King (manager)
2015-09-09 09:26

 For what would such a hook be used? We do *not* want to allow projects to try to do their own updates on the CMake-generated files. Such projects would break if we change the way the files are generated. If there is some useful change that can be made to the generated files then one should contribute a feature to CMake to generate it that way directly instead.
(0039382)
Gregory Kramida (reporter)
2015-09-09 16:15
edited on: 2015-09-09 16:22

 Well, I don't know... Here goes.

The way that CMake generates eclipse CDT projects causes issues when it comes to working with the source & header files.

Please take a look at this "bug" here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=471990 [^]

The only way I see to solve it is to add a filter (as reported above) on the [Subprojects] virtual folder. The filter gets removed every time the project is re-generated with CMake. The only work-around I could think of was writing a python script that would add the filter manually to the .project XML file. This script would need to be triggered after the project is generated with CMake.

If you think there's no sense in adding post-generation steps, then should I report this as a bug instead?
(0039383)
Brad King (manager)
2015-09-09 16:26

 Re 0015725:0039382:

> way that CMake generates eclipse CDT projects causes issues

CMake should be fixed to resolve this. Any filtering you add in a post-generate step could be broken at any time by CMake changing details of the project generation.

There are a few other open issues in this issue tracker about Eclipse projects. Please search for them to see if this has already been reported and otherwise open a separate issue.
(0040393)
Robert Maynard (manager)
2016-02-01 09:10

 Closing resolved issues that have not been updated in more than 4 months.

 Issue History
Date Modified Username Field Change
2015-09-03 12:11 Gregory Kramida New Issue
2015-09-09 09:26 Brad King Note Added: 0039375
2015-09-09 16:15 Gregory Kramida Note Added: 0039382
2015-09-09 16:16 Gregory Kramida Note Edited: 0039382
2015-09-09 16:22 Gregory Kramida Note Edited: 0039382
2015-09-09 16:26 Brad King Note Added: 0039383
2015-09-09 16:26 Brad King Status new => resolved
2015-09-09 16:26 Brad King Resolution open => won't fix
2016-02-01 09:10 Robert Maynard Note Added: 0040393
2016-02-01 09:10 Robert Maynard Status resolved => closed

Copyright © 2000 - 2018 MantisBT Team