Oh ... I dunno. I installed it with the installer from the web site, took the default options. Then I unzipped the source to 'c:\code\tools\cmake' and tried building it. It built once successfully, but the second time through it threw that error.
That doesn't seem very far off the beaten path to me ... and no, I haven't gotten as far modifying cmake enough to break it yet at that point. And why would it find all the other tools, but not find CPack? -----Original Message----- From: Bill Hoffman [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 08, 2007 3:06 PM To: Rob Mathews Cc: Bill Hoffman; [email protected] Subject: Re: [CMake] Creating project distribution using cpack. Rob Mathews wrote: > That's easy. In CMake.cxx, in or around line 2310-2317 > > /* > I don't need this and CMake can't find it (even though I installed > correctly). > if (!cmSystemTools::FileExists(this->CPackCommand.c_str())) > { > cmSystemTools::Error("Cannot find the CPack executable"); > this->CPackCommand = "CPACK-COMMAND-NOT-FOUND"; > } > */ > > I've read what CPack does, and our development environment has a > different way of doing that, so I don't need it and don't want to force > all of our developers to install it. > > Hence the comment. And I can tell from the code that isn't a switch to > turn it off. > OK, then, I would say that it was not installed correctly or the sources have been modified in some way that breaks this. If you build stock CMake, I have never seen it not find cpack. On the other hand, since cpack/cmake/ctest are meant to be a family of tools, it is unlikely that this change will make it into the CVS for CMake. As, not having it when it is supposed to be there is a symptom of some other problem. -Bill _______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
