Hi, what about an install-recursive target. We 'injected' such a target manually in our autotools-based environment, and while it's probably possible to generate such a target manually in cmake, too (using macros), it would be a nice default-feature.
Idea: if you're somewhere in the build tree, install-recursive will install (and build, if out of date) all targets the targets in the current directory depend on and then do a make install locally. cheers, Manuel > On Tuesday 6 June 2006 11:09, you wrote: >> I'm not sure we didn't misunderstand. >> >> I suggested to turn the option CMAKE_SKIP_INSTALL_ALL_DEPENDENCY in >> KDEs cmake files on. This will have the effect that if you "make >> install" in some subdir, it will try to install in this subdir and >> nothing else. I.e. it will not try to build in this subdir (and also >> not in subdirs the current subdir depends on). > > Yes, I did't make clear that I understood that. Sorry. > Doing that will require people to always type 'make all' and then a 'make > install'. > I'm pretty sure that this is going to give people big question marks above > their heads since thats a logical dependency. Make install should always > depend on make all. > > To put this in perspective; I asked for a make target to install one > specific library, which includes the compiling of the right sourcefiles > needed for that. > This feature is not possible in cmake and all suggestions made in this > thread either disrupt the normal workflow or just do a lot of work thats > not needed. > If the /fast is available then that will ease the pain already somewhat :) > -- > Thomas Zander > _______________________________________________ > CMake mailing list > [email protected] > http://www.cmake.org/mailman/listinfo/cmake _______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
