MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0003316CMakeCMakepublic2006-06-02 12:152016-06-10 14:30
ReporterThomas Zander 
Assigned ToBrad King 
PriorityhighSeverityfeatureReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0003316: Allow compiles concurrent, but not linking.
DescriptionIn usermake there is a feature that is needed for distributed compiling. Its a feature that allows similar results to make -j, but with a twist; the compile jobs are started concurrently but the buildsystem makes sure there is only one link-job going on at the same time.

The result of this is that the multiple compiles go into the compile farm (and don't cause any load on my local CPU) and the linking, which is always done locally will not overload the system because there is only one.

I only care for such a system for the (g)make target.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2012-08-13 10:36Brad KingStatusassigned => backlog
2012-08-13 10:36Brad KingNote Added: 0030516
2016-06-10 14:27Kitware RobotNote Added: 0041313
2016-06-10 14:27Kitware RobotStatusbacklog => resolved
2016-06-10 14:27Kitware RobotResolutionopen => moved
2016-06-10 14:30Kitware RobotStatusresolved => closed

Notes
(0004163)
Bill Hoffman   
2006-06-02 12:32   
This is more difficult to do, but we are thinking about ideas. Perhaps some sort of mutex that is put around the linking stuff. There is not a good way to do it from the makefiles. If you have any suggestions on how to implement this with gmake, post them here.
(0030516)
Brad King   
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.
(0041313)
Kitware Robot   
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.