[cmake-developers] make install starts "too" late
Alexander Neundorf
neundorf at kde.org
Thu Aug 10 14:29:50 EDT 2006
Hi,
http://bugs.kde.org/show_bug.cgi?id=132072
Thomas complains that make install does at first "make all" for the whole
project, then "make install" for the whole project.
He would prefer if it would do this per-directory, i.e. enter a directory,
make all, make install there.
If I understand correctly, the advantage there is that some stuff is already
installed while other things are still compiling and so he can test the
already installed stuff faster.
(KDE apps usually don't work uninstalled for various reasons, desktop files,
ui files, ...)
What do you think of this ?
Another idea would be to change the cmake_install.cmake file a bit:
cmake_install.cmake:
# Install script for directory: /home/alex/src/kde4-svn/KDE/kdebase/kmenuedit
...
# setup some variables
INCLUDE("/home/alex/src/kde4-svn/buildKDE/kdebase/kmenuedit/cmake_install_local.cmake")
# Include the install script for each subdirectory.
INCLUDE("/home/alex/src/kde4-svn/buildKDE/kdebase/kmenuedit/pixmaps/cmake_install.cmake")
and have all the actual install commands for the current directory be
generated in cmake_install_local.cmake ?
Then the "advanced" user would be able to run "cmake -P
cmake_install_local.cmake" and install only what is in the current directory
without having to wait for all subdirs to finish compiling.
If you think this would be ok, I can send a patch.
Bye
Alex
--
Work: alexander.neundorf AT jenoptik.com - http://www.jenoptik-los.de
Home: neundorf AT kde.org - http://www.kde.org
alex AT neundorf.net - http://www.neundorf.net
More information about the cmake-developers
mailing list