So it actually *was* a permissions issue after all...
On Wed, Jan 6, 2010 at 8:56 AM, Joe L <superist_...@yahoo.com> wrote: > Trying to open the solution file (trycompile generated) didn't work by > double clicking on it, so I searched about that and found this: > > http://www.pluralsight.com/community/blogs/matt/archive/2007/05/21/47446.aspx > > this comment is the one that solved that for me: > "It works when you set both > Launcher (C:\Program Files\Common Files\Microsoft > Shared\MSEnv\VSLauncher.exe) and IDE(C:\Program Files\Microsoft Visual > Studio 8\Common7\IDE\devenv.exe) to run as administrator. > (Right click .exe and select Propertries -> Compatibility, and choose Run > as Administrator) > > Hope this helps. " > > After doing this I thought to set cmake as 'run as admin', and that seemed > to get everything to generate as it should. > > Thanks, > Joe > > ------------------------------ > *From:* Bill Hoffman <bill.hoff...@kitware.com> > *To:* David Cole <david.c...@kitware.com> > *Cc:* cmake@cmake.org > *Sent:* Tue, January 5, 2010 3:01:47 PM > > *Subject:* Re: [CMake] Compiler Test Failing on Windows 7 > > David Cole wrote: > > On Tue, Jan 5, 2010 at 12:38 PM, Hendrik Sattler < > p...@hendrik-sattler.de <mailto:p...@hendrik-sattler.de>> wrote: > > > > Am Dienstag 05 Januar 2010 14:09:00 schrieb Joe L: > > > C:/Program Files (x86)/CMake > > > 2.8/share/cmake-2.8/Modules/CMakeTestCXXCompiler.cmake:62 > > > (CMAKE_DETERMINE_COMPILER_ABI) CMakeLists.txt:3 (PROJECT) > > > > You might want to avoid instal cmake in a path with spaces. > > I install software with unix layout to "C:\local" > > > > > > Nonsense. CMake works fine in a directory that has spaces in its name. We > wouldn't make the default installation directory on Windows have spaces in > it if it did have problems... > > > > There must be something else going on here. > > > > > > This has nothing to do with copy file not working. The copy file is not > working because no executable was generated for some reason. You should > look in CMakeError.log and CMakeOutput.log. If that fails to show anything, > then run cmake --debug-trycompile, then go into the CMakeFiles directory and > run the build tool by hand and figure out why it is not producing executable > files. > > -Bill > > -- Bill Hoffman > Kitware, Inc. > 28 Corporate Drive > Clifton Park, NY 12065 > bill.hoff...@kitware.com > http://www.kitware.com > 518 881-4905 (Direct) > 518 371-3971 x105 > Fax (518) 371-4573 > _______________________________________________ > 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://www.cmake.org/mailman/listinfo/cmake > >
_______________________________________________ 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://www.cmake.org/mailman/listinfo/cmake
