From: Jim G. <jg...@ro...> - 2009-01-08 19:23:11
|
I have been using Visual Studio 2005 to build VXL very successfully. But now I have the opportunity to upgrade to Visual Studio 2008. Has anyone used VS 2008 to build VXL successfully? If not, I will stay with VS 2005, using the "if it's not broken, don't fix it" approach. Thanks, Jim Green |
From: Ian S. <ian...@st...> - 2009-01-09 09:54:04
|
I've been using it with VC2008 for at least six months without any problems. Ian. Jim Green wrote: > I have been using Visual Studio 2005 to build VXL very > successfully. But now I have the opportunity to upgrade to Visual > Studio 2008. Has anyone used VS 2008 to build VXL successfully? If > not, I will stay with VS 2005, using the "if it's not broken, don't > fix it" approach. > > Thanks, Jim Green > > > ------------------------------------------------------------------------------ > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > _______________________________________________ > Vxl-users mailing list > Vxl...@li... > https://lists.sourceforge.net/lists/listinfo/vxl-users |
From: Jim G. <jg...@ro...> - 2009-01-10 23:20:22
|
Ian, Are you using Visual Studio 9 (2008) or Visual Studio 8 (2005)? What version of CMake are you using to build the vxl.sln file to load into VC++? I installed VS9 2008 and CMake 2.6.2 fails to configure VXL because the initial compiler test fails to find the compiler executable "cl.exe" although it is in one of the VC sub-directories. I had to download a newer version of CMake, version 2.6.2, because the version I had been using with VS8 2005, version 2.4.6, does not support VS9 2008. Unless someone knows anything about this, I guess I will just remove VS9 2008 and re-install VS8 2005. I wanted to try VS9 2008 because VS8 had a problem with intellisense hanging on such a large project and I hoped M$ had fixed that problem in VS9 Thanks, Jim Green ------------------------------------ At 04:53 AM 1/9/2009, you wrote: >I've been using it with VC2008 for at least six months without any problems. > >Ian. > >Jim Green wrote: >>I have been using Visual Studio 2005 to build VXL very >>successfully. But now I have the opportunity to upgrade to Visual >>Studio 2008. Has anyone used VS 2008 to build VXL >>successfully? If not, I will stay with VS 2005, using the "if it's >>not broken, don't fix it" approach. >>Thanks, Jim Green >> >>------------------------------------------------------------------------------ >>Check out the new SourceForge.net Marketplace. >>It is the best place to buy or sell services for >>just about anything Open Source. >>http://p.sf.net/sfu/Xq1LFB >>_______________________________________________ >>Vxl-users mailing list >>Vxl...@li... >>https://lists.sourceforge.net/lists/listinfo/vxl-users |
From: Amitha P. <ami...@us...> - 2009-01-11 00:07:52
|
I personally use VS 8 (2005), but colleagues use VS 9 (2008), and AFAIK they had no issues configuring or compiling vxl with CMake 2.6. Amitha. |
From: Jim G. <jg...@ro...> - 2009-01-11 00:47:49
|
Ian, Are you using Visual Studio 9 (2008) or Visual Studio 8 (2005)? What version of CMake are you using to build the vxl.sln file to load into VC++? I installed VS9 2008 and CMake 2.6.2 fails to configure VXL because the initial compiler test fails to find the compiler executable "cl.exe" although it is in one of the VC sub-directories. I had to download a newer version of CMake, version 2.6.2, because the version I had been using with VS8 2005, version 2.4.6, does not support VS9 2008. Unless someone knows anything about this, I guess I will just remove VS9 2008 and re-install VS8 2005. I wanted to try VS9 2008 because VS8 had a problem with intellisense hanging on such a large project and I hoped M$ had fixed that problem in VS9. Thanks, Jim Green ------------------------------------ At 04:53 AM 1/9/2009, Ian Scott wrote: >I've been using it with VC2008 for at least six months without any problems. > >Ian. > >Jim Green wrote: >>I have been using Visual Studio 2005 to build VXL very >>successfully. But now I have the opportunity to upgrade to Visual >>Studio 2008. Has anyone used VS 2008 to build VXL >>successfully? If not, I will stay with VS 2005, using the "if it's >>not broken, don't fix it" approach. >>Thanks, Jim Green |
From: Miguel A. Figueroa-V. <mi...@ie...> - 2009-01-11 04:05:28
|
On Sat, Jan 10, 2009 at 7:13 PM, Jim Green wrote: > Ian, > > Are you using Visual Studio 9 (2008) or Visual Studio 8 (2005)? What > version of CMake are you using to build the vxl.sln file to load into VC++? > > I installed VS9 2008 and CMake 2.6.2 fails to configure VXL because > the initial compiler test fails to find the compiler executable > "cl.exe" although it is in one of the VC sub-directories. I had to > download a newer version of CMake, version 2.6.2, because the version > I had been using with VS8 2005, version 2.4.6, does not support VS9 2008. > > Unless someone knows anything about this, I guess I will just remove > VS9 2008 and re-install VS8 2005. I wanted to try VS9 2008 because > VS8 had a problem with intellisense hanging on such a large project > and I hoped M$ had fixed that problem in VS9. Well, I'm also using VS9 now with a current cvs build of CMake without any problems. However, if it is not detecting the compiler, then it most likely a problem with your VS9 or CMake configuration. I would create a very simple project and try to build with CMake. Something like: -------- //CMakeLists.txt project(test) add_executable(tester tester.cxx) -------- If you still have problems getting this configured with CMake, then maybe the CMake list is the appropriate place to address this. Hope that helps. --Miguel > > At 04:53 AM 1/9/2009, Ian Scott wrote: >>I've been using it with VC2008 for at least six months without any problems. >> >>Ian. >> >>Jim Green wrote: >>>I have been using Visual Studio 2005 to build VXL very >>>successfully. But now I have the opportunity to upgrade to Visual >>>Studio 2008. Has anyone used VS 2008 to build VXL >>>successfully? If not, I will stay with VS 2005, using the "if it's >>>not broken, don't fix it" approach. >>>Thanks, Jim Green |
From: Jim G. <jg...@ro...> - 2009-01-11 01:13:53
|
Amitha, Thanks, I will look into CMake further to see if I can determine why it can't find the VS C++ compiler file to use. Maybe there is some initial setup of CMake 2.6 that I didn't do. Thanks, Jim Green ------------------------------------------ At 07:07 PM 1/10/2009, Amitha Perera wrote: >I personally use VS 8 (2005), but colleagues use VS 9 (2008), and >AFAIK they had no issues configuring or compiling vxl with CMake 2.6. > >Amitha. |
From: Jim G. <jg...@ro...> - 2009-01-11 21:06:40
|
Miguel, Thanks for the suggestions. But I took a slightly different approach. I looked into this problem a little more and believe I have isolated it as a VS9 Setup problem. But first a little history. I started using VXL about a year and a half ago. At that time my OS was Win2000 and I had installed VS 2005 (aka VS8) and Cmake 2.4.6. No problems, everything built in CMake and VS8. But about a month ago I decided I should upgrade OS to WinXP 32-bit. I had to do a clean install on a new disk, new partition, and re-install the software I needed to that new partition. (Right now I can dual boot into either the Win2000 or WinXP-32 disks.) I made a copy of my VXL partition to use with WinXP so I wouldn't corrupt the stuff that was working under Win2000. But at a M$ launch event last year M$ gave out a free copy of VS9 Standard edition and I wanted to try that, so a couple days ago I installed it along with the VS9 SP1. (I also downloaded CMake 2.6.2 (the latest release version because 2.4 doesn't support VS9.) Things immediately didn't go well. I tried to produce a vxl.sln file with CMake and got this error string: -------------------------------------------------------- Determining if the C compiler works failed with the following output: Change Dir: D:/cvsroot/bin/CMakeFiles/CMakeTmp Run Build Command:C:\VisStudio08\Common7\IDE\devenv.com CMAKE_TRY_COMPILE.sln /build Debug /project cmTryCompileExec Microsoft (R) Visual Studio Version 9.0.21022.8. Copyright (C) Microsoft Corp. All rights reserved. 1>------ Build started: Project: cmTryCompileExec, Configuration: Debug Win32 ------ 1>Compiling... 1>Project : error PRJ0003 : Error spawning 'cl.exe'. 1>Build log was saved at "file://d:\cvsroot\bin\CMakeFiles\CMakeTmp\cmTryCompileExec.dir\Debug\BuildLog.htm" 1>cmTryCompileExec - 1 error(s), 0 warning(s) ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== ------------------------------------------------------------- It appeared that CMake couldn't find the compiler file, cl.exe. I did a little searching around the internet and found that file should be located in: C:\VisStudio08\VC\bin But it wasn't there. I searched C:\VisStudio08 for cl.exe and found 2 instances, one in each of: C:\VisStudio08\VC\bin\amd64 C:\VisStudio08\VC\bin\x86_amd64 (By now you have guessed I have an AMD Athlon 64 X2 dual core chip, about 2 years old. It worked great under Win2000, VS 2005 and CMake 2.4.6.) So I decided to copy the cl.exe file from /bin/x86_amd64 into /bin and see what happened. (I also copied cl.exe.config and clui.dll) I still got an error, CMake found the compiler but didn't like one of the compiler switches. But the key information here is that when the compiler started, it identified itself as a compiler which produces X64 64-bit code, not i86 32-bit code? (See below where it reports "Optimizing Compiler Version 15.00.21022.08 for x64") Apparently the compile switches are slightly different for the 32 and 64 bit versions causing the CMake test to fail. ---------------------------------------------------------- Determining if the C compiler works failed with the following output: Change Dir: D:/cvsroot/bin/CMakeFiles/CMakeTmp Run Build Command:C:\VisStudio08\Common7\IDE\devenv.com CMAKE_TRY_COMPILE.sln /build Debug /project cmTryCompileExec Microsoft (R) Visual Studio Version 9.0.21022.8. Copyright (C) Microsoft Corp. All rights reserved. 1>------ Build started: Project: cmTryCompileExec, Configuration: Debug Win32 ------ 1>Compiling... 1>Microsoft (R) C/C++ Optimizing Compiler Version 15.00.21022.08 for x64 1>Copyright (C) Microsoft Corporation. All rights reserved. 1>cl /Od /D "WIN32" /D "_WINDOWS" /D "_DEBUG" /D "CMAKE_INTDIR=\"Debug\"" /D "_MBCS" /FD /RTC1 /MDd /Fo"cmTryCompileExec.dir\Debug\\" /Fd"D:/cvsroot/bin/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec.pdb" /W3 /c /Zi /TC /Zm1000 1> .\testCCompiler.c 1>testCCompiler.c 1>c1 : fatal error C1048: unknown option 'L' in '-ZILP448' 1>Build log was saved at "file://d:\cvsroot\bin\CMakeFiles\CMakeTmp\cmTryCompileExec.dir\Debug\BuildLog.htm" 1>cmTryCompileExec - 1 error(s), 0 warning(s) ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== -------------------------------------------------------------------------- So I have concluded that VS9 Setup installed the wrong (64 bit) compilers for my (32-bit) OS and didn't install the 32-bit one. My solution is to uninstall all this mess and just use my old VS 2005 which worked great. Regards, Jim Green ------------------------------------------------------------ At 11:05 PM 1/10/2009, Miguel A. Figueroa-Villanueva wrote: >On Sat, Jan 10, 2009 at 7:13 PM, Jim Green wrote: > > Ian, > > > > Are you using Visual Studio 9 (2008) or Visual Studio 8 (2005)? What > > version of CMake are you using to build the vxl.sln file to load into VC++? > > > > I installed VS9 2008 and CMake 2.6.2 fails to configure VXL because > > the initial compiler test fails to find the compiler executable > > "cl.exe" although it is in one of the VC sub-directories. I had to > > download a newer version of CMake, version 2.6.2, because the version > > I had been using with VS8 2005, version 2.4.6, does not support VS9 2008. > > > > Unless someone knows anything about this, I guess I will just remove > > VS9 2008 and re-install VS8 2005. I wanted to try VS9 2008 because > > VS8 had a problem with intellisense hanging on such a large project > > and I hoped M$ had fixed that problem in VS9. > >Well, I'm also using VS9 now with a current cvs build of CMake without >any problems. > >However, if it is not detecting the compiler, then it most likely a >problem with your VS9 or CMake configuration. I would create a very >simple project and try to build with CMake. Something like: > >-------- >//CMakeLists.txt >project(test) >add_executable(tester tester.cxx) >-------- > >If you still have problems getting this configured with CMake, then >maybe the CMake list is the appropriate place to address this. > >Hope that helps. > >--Miguel > > > > > At 04:53 AM 1/9/2009, Ian Scott wrote: > >>I've been using it with VC2008 for at least six months without > any problems. > >> > >>Ian. > >> > >>Jim Green wrote: > >>>I have been using Visual Studio 2005 to build VXL very > >>>successfully. But now I have the opportunity to upgrade to Visual > >>>Studio 2008. Has anyone used VS 2008 to build VXL > >>>successfully? If not, I will stay with VS 2005, using the "if it's > >>>not broken, don't fix it" approach. > >>>Thanks, Jim Green |
From: Jim G. <jg...@ro...> - 2009-01-16 23:21:27
|
I fell back to Vis Studio 2005, and CMake now makes the vxl.sln file with no problems. Then the vxl.sln file loads into Vis Studio 2005 with no problem. But, when I try to build a Brown contrib executable which has always built before with no problem, I get an "error" message from the C++ compiler saying: WINVER not defined. Defaulting to 0x0502 (Windows Server 2003) This "error" message occurs a dozen or so times. Of course. I'm running Win XP with SP3. The WINVER for XP is 0x0501. Before when I was running Win 2000 (for 8 years) I never had any such error message, I never had to set WINVER, and everything built great. (I'm also getting another error which I suspect is due to this.) Has anyone else ever seen this "error" when building VXL in Visual Studio? Thanks, Jim Green ----------------------------------- |
From: Jim G. <jg...@ro...> - 2009-01-17 19:20:23
|
Interesting steps to solve my problem below. I looked at the VS MSDN help file and discovered that there is a compile switch /D that allows you to set the WINVER. I had never needed to do this with my Win2000 install of the same VS software, CMake under Win2000 doesn't need it, but I added /D WINVER=0x0501 to the CMake compile switches and the error went away. However, the other error did not disappear. It was a can't read an .h file from the Vis Studio directory (the file is there and has read permissions for everybody) which caused a bunch of compile errors. Never had this problem with my Win2000 install of the same VS software. I think this is an example of the wisdom of the old saying, "if it's not broken, don't fix it". I fixed it and got a bunch of problems. So I just fell back and booted up my Win2000 partition, updated the VXL source there, ran CMake (no problem) and built the app (no problem). Then ran the app (no problem). I can't understand why Microsoft keeps making changes that break things that work? I have built this app with VS2005 running under WinXP before with no problem, but I didn't do the installs so have no idea what the sys manager did to make it work under XP. It shouldn't be that difficult, but it is. At any rate, I don't mind booting up Win2000 to do my builds, so that's what I'll do. Regards, Jim Green --------------------------------------- At 05:21 PM 1/16/2009, Jim Green wrote: >I fell back to Vis Studio 2005, and CMake now makes the vxl.sln file >with no problems. Then the vxl.sln file loads into Vis Studio 2005 >with no problem. But, when I try to build a Brown contrib executable >which has always built before with no problem, I get an "error" >message from the C++ compiler saying: > >WINVER not defined. Defaulting to 0x0502 (Windows Server 2003) > >This "error" message occurs a dozen or so times. > >Of course. I'm running Win XP with SP3. The WINVER for XP is >0x0501. Before when I was running Win 2000 (for 8 years) I never had >any such error message, I never had to set WINVER, and everything >built great. (I'm also getting another error which I suspect is due to this.) > >Has anyone else ever seen this "error" when building VXL in Visual Studio? > >Thanks, Jim Green >----------------------------------- > > >------------------------------------------------------------------------------ >This SF.net email is sponsored by: >SourcForge Community >SourceForge wants to tell your story. >http://p.sf.net/sfu/sf-spreadtheword >_______________________________________________ >Vxl-users mailing list >Vxl...@li... >https://lists.sourceforge.net/lists/listinfo/vxl-users |