Actually, I realize the problem here - you are assuming that one would build the full toolset, and I simply built only CMake because I only needed CMake and didn't want to wait for the rest of the compile. Thus, the first time it ran because it use the defaults from the installation, but the next it didn't run because it was using the new partially built directory.
-----Original Message----- From: Bill Hoffman [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 08, 2007 3:39 PM To: Rob Mathews Cc: Bill Hoffman; [email protected] Subject: Re: [CMake] Creating project distribution using cpack. Rob Mathews wrote: > 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? > That should work, and works well for many people using cmake from CVS. If you are interested in getting to the bottom of the problem, I can help. But I don't think just removing the check is the right solution, as theoretically it actually built cpack, and it was in the right place. I am not saying there is not a bug here, but I would like to find the real problem if possible. If I follow the steps you give, I have no problem. Of course, I do not know what compiler versions and options you were using. -Bill _______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
