MantisBT - CMake
View Issue Details
0008343CMakeCMakepublic2009-01-04 15:382016-06-10 14:30
Aaron Seigo 
Brad King 
normalfeaturehave not tried
closedmoved 
CMake-2-6 
 
0008343: Option to forego full dependency checking on build
While the dependency checking that happens when starting a build is terrific for casual developers or software one builds intermittently, it can cost fairly significant amounts of time when working on a module with several internal dependencies.

For instance, in the kdelibs source package, the plasma library depends on kdecore, kdeui, kio, kfile, knewstuff. All of these are checked on every build, and they are all non-trivial libraries themselves. As someone who might rebuild the plasma library (and only that library) dozens of times a day during the course of development, this lag adds up considerably.

There is a make ${PROJECT}/fast, but no corresponding trick for install, and this must be repeated every time the build is started (meaning I have to change make -j4 plasma/fast to make -j4 knewstuff/fast if I'm switching about).

While it makes all the sense in the world to have the dependency checking there by default, it would be great if there was a way to turn off this checking altogether, leaving it up to the developer at that point. The option could be scary looking and long to discourage use, even:-DCMAKE_NO_DEP_CHECKS_BETWEEN_MODULES_AT_BUILD ;)

A /fast install would be similarly useful.
No tags attached.
Issue History
2009-01-04 15:38Aaron SeigoNew Issue
2009-01-15 15:28Bill HoffmanStatusnew => assigned
2009-01-15 15:28Bill HoffmanAssigned To => Brad King
2009-01-15 16:05Brad KingNote Added: 0014575
2009-01-15 16:16Aaron SeigoNote Added: 0014576
2009-01-15 16:31Brad KingNote Added: 0014577
2009-01-15 16:42Aaron SeigoNote Added: 0014579
2009-01-15 16:55Brad KingNote Added: 0014580
2012-08-13 10:36Brad KingStatusassigned => backlog
2012-08-13 10:36Brad KingNote Added: 0030497
2016-06-10 14:27Kitware RobotNote Added: 0041489
2016-06-10 14:27Kitware RobotStatusbacklog => resolved
2016-06-10 14:27Kitware RobotResolutionopen => moved
2016-06-10 14:30Kitware RobotStatusresolved => closed

Notes
(0014575)
Brad King   
2009-01-15 16:05   
There is "make install/fast".

Currently there is "make mylib/fast" as you say. How will a lack of dependencies between modules help avoid specifying the target name to build?
(0014576)
Aaron Seigo   
2009-01-15 16:16   
> There is "make install/fast".

bwuha! this is new, then; i look forward to seeing this after my next cmake upgrade. thanks =)

> Currently there is "make mylib/fast" as you say. How will a lack of
> dependencies between modules help avoid specifying the target name to build?

here's the use case:

cd kdelibs/plasma
make -j4 plasma/fast && sudo make install
cd ../kfile
!make
*error* // oops!
make -j4 kfile/fast && sudo make install
cd -
make -j4 plasma/fast && sudo make install

repeat into tedium. especially as i work between multiple modules throughout the day, it gets a little boring ;)

being able to simply say "i'd like cmake to assume fast builds in this module until a make edit_cache and change that" would render this down to:

cd kdelibs/plasma
make -j4 && sudo make install
cd ../kfile
!make
cd -
!make

aah! life is beautiful again. yes, this is completely 100% sugar on top, but it would be very welcome sugar. less typing == a faster, happier aaron. not that your job in life is to make me happy, of course ;), though i assume i'm not unique in this fashion. well, i know i'm not from conversation with others.

obviously not a hyper critical issue, just a nice touch to see one day should you deem it worthwhile as well.

cheers ....
(0014577)
Brad King   
2009-01-15 16:31   
What version of CMake are you using now?
(0014579)
Aaron Seigo   
2009-01-15 16:42   
aseigo@independence:~> cmake -version
cmake version 2.6-patch 2
(0014580)
Brad King   
2009-01-15 16:55   
The "make install/fast" feature has been around since no later than 2006. It should be in 2.6.2. It even works in subdirectories (installs just that dir and below).
(0030497)
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.
(0041489)
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.