From: Jim G. <jgreen@RobotVision.com> - 2006-08-25 15:08:25
|
I'll try to be as detailed as possible. I'm trying to build/install VXL on a AMD X2 4400+ chip box with 2GB RAM running Win2000 SP-4 (I have WinXP-64 but haven't had time to install it yet). I have M$ visual studio 2005 (version 8) and CMake 2.4 patch 3 installed. I try to run CMakeSetup.exe. I specify D:\vxl\vxl-1.6 as $VXLSRC and D:\vxl\bin as $VXLBIN in the two places in CMake. I press Configure and "Visual Studio 8 2005" appears in the "Build For" slot in a pop-up window (which is what I have installed on the box). I press OK and CMake begins grinding, displaying a number of strings in the status bar at the bottom. After several minutes, a number of options appear in red in the Cache Values window. About 24 of these lines are "something-NOTFOUND" values, "something" being either LIBRARY, INCLUDE_DIR, INCLUDE_PATH, or some such string. I click Confugure again without changing any values and the Cache Value items change to grey, but the NOT-FOUNDSs are still listed. It pauses again and the OK button is now not greyed out. I press OK and CMake finishes and the window dissapears. Should I be concerned about these NOT-FOUND values? I then check D:\vxl\bin and there are a bunch of files, but no vxl.dsw file. There is a vxl.sin but no file with the .dsw extension. There is no *.dsw file in the entire D:\vxl tree. The "Installing the VXL 1.6 release" instructions clearly state that I should load the vxl.dsw file into visual studio. I load the vxl.sin file as a project and it loads(!!??) I then build=>build_all and visual studio grinds compiling and linking for a while, outputting thousands of lines in the Output window. After about 10 minutes it finished with: 418>------ Build started: Project: ALL_BUILD, Configuration: Debug Win32 ------ 418>Performing Post-Build Event... 418>"Build all projects" 418>Build log was saved at "file://d:\vxl\bin\ALL_BUILD.dir\Debug\BuildLog.htm" 418>ALL_BUILD - 0 error(s), 0 warning(s) ========== Build: 418 succeeded, 0 failed, 0 up-to-date, 0 skipped ========== Apparently it built successfully, but the install instructions do not match what happened. My question: was this a successful build? If so, why all the NOT-FOUND values in CMake? Thanks, Jim Green -------------------------------- |
From: Miguel A. Figueroa-V. <mi...@ie...> - 2006-08-25 17:54:31
|
Hello Jim, These are basic questions about CMake and Visual Studio. I'll answer as best I can below, but in essence you are doing it right and have a successful build. On 8/25/06, Jim Green <jg...@ro...> wrote: > I try to run CMakeSetup.exe. I specify D:\vxl\vxl-1.6 as $VXLSRC and > D:\vxl\bin as $VXLBIN in the two places in CMake. I press Configure > and "Visual Studio 8 2005" appears in the "Build For" slot in a > pop-up window (which is what I have installed on the box). I press > OK and CMake begins grinding, displaying a number of strings in the > status bar at the bottom. After several minutes, a number of options > appear in red in the Cache Values window. About 24 of these lines > are "something-NOTFOUND" values, "something" being either LIBRARY, > INCLUDE_DIR, INCLUDE_PATH, or some such string. I click Confugure > again without changing any values and the Cache Value items change to > grey, but the NOT-FOUNDSs are still listed. It pauses again and the > OK button is now not greyed out. I press OK and CMake finishes and > the window dissapears. Should I be concerned about these NOT-FOUND values? Most of the NOT-FOUND values are variables for different optional components of VXL. The first time cmake runs it puts these values on top and in red so that you pay attention to them and if available (e.g., DirectShow, etc.) but not found you have the opportunity to tell cmake where it is. But the build process will not compile in support of that particular component if it is not found and you don't specify it either. > > I then check D:\vxl\bin and there are a bunch of files, but no > vxl.dsw file. There is a vxl.sin but no file with the .dsw > extension. There is no *.dsw file in the entire D:\vxl tree. The > "Installing the VXL 1.6 release" instructions clearly state that I > should load the vxl.dsw file into visual studio. > > I load the vxl.sin file as a project and it loads(!!??) I then > build=>build_all and visual studio grinds compiling and linking for a > while, outputting thousands of lines in the Output window. After > about 10 minutes it finished with: I think it is vxl.sln and this is visual studio workspace file since visual studio 7. VS 6.0 used the .dsw, but not the 7.0+ versions. --Miguel |