>> Your scripts would still only work for one target... since you'd have to > pick one to build the rest of the package around, so if I have a build > product that has a dozen utilities, rather than having one place they can > all work from, I have now to either duplicate all files to all runnable > targets or have a central one that would be the only one to work. This is > more of a hack.
I don't think this is true at all. My scripts do the "right" thing when you build and they are efficient. But I still respect INSTALL and you can still install. I still use INSTALL and PACKAGE, particularly the latter on Windows for creating an NSIS installer. Thanks, Eric -- Beginning iPhone Games Development http://playcontrol.net/iphonegamebook/ -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
