2012/7/12 David Cole <david.c...@kitware.com>: > I pushed this to 'next' the other day, but the test failures on dashmacmini3 > remain, so the latest commit is not having its intended effect. > > Back to Bill's original assertion: > "I am not sure how this works on a fresh build tree either as cpack won't > even exist."
Yes Bill is right, I did check that but may be not thoroughly enough. CPack/CMake etc... is installed at several place on my dev system next time I'll check that no install cpack command may be used during CMake fresh build. > It must work on fresh build trees, because all of our Nightly dashboards > work from fresh build trees. Since those work (even before this recent > branch), there must be something else going on here. May be. The problem I see here "generic" CMake is bootstrapped CPack is not, if it was we could assume that CPack *is* available when CMake is. > We're not going to merge this into 'master' until we get it right... I'll > take a look at this tomorrow if you don't have time to spend on it right > now, Eric. Sorry for the delayed answer. This is a good decision as usual. I have not enough spare time right now and probably not much before July 20th... I'm organizing a conference and this eats most of my time. -- Erk Le gouvernement représentatif n'est pas la démocratie -- http://www.le-message.org -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
