Difference between revisions of "User talk:Bubblesort Triskaidekaphobia"

Revision as of 23:02, 5 November 2009

I build and script and run my university's sim. Recently I compiled a viewer, but I barely know enough to code a hello, world program in C++. Compiling is not simple or easy for a beginner. I took a lot of notes on my experience and I'm pasting them here. I'll work on the document and clean it up until it's readable and then I plan to go and edit the appropriate wiki pages so that they are more helpful. I'm posting and editing this publicly for the world to see because it might help somebody, even if it isn't polished. Bubblesort Triskaidekaphobia 06:41, 6 November 2009 (UTC)

Raw Log of my Compiling Experience:

I started out by going to the official secondlife wiki and following the directions to download and install

Visual Studio 2005 Express. Here is the link to the instructions I'm following:

http://wiki.secondlife.com/wiki/Microsoft_Visual_Studio

Here is how it went. I list the heading the instructions in quesiton are under and then write about problems I

had with it.

I'm running Windows Vista Ultimate x86 on a dual proc 5200+ 64 bit AMD, 3 GB of RAM and an NVIDIA GEFORCE 6150SE nForce 430 video card.

Download Express:

The link to download Visual C++ Express was good, but the install failed multiple times when I tried to install

SQL server. I've had problems with SQL installs before when working on other projects, and I decided that SQL

is probably not important to the task at hand, so I just ran the install without the SQL and it installed fine.

The service pack links on the wiki page were not good. They downloaded the service packs ok, but when I ran

them they could not detect Visual C++.

I got the service packs by running windows update about 3 or 4 times, rebooting each time.

Install Microsoft Platform & Direct X SDKs:

These downloaded and installed fine.

Setup the project globals:

The site does not specify where the globals are located, so I did my best with what I had. I needed to set up

includes and libraries paths to include the following things in the following order:

1. Platform SDK paths $(VCInstallDir)PlatformSDK\include was already listed, but just to make sure I added C:\Program

Files\Microsoft SDKs\Windows\v6.1\Lib to the line right after it.

2. DirectX SDK paths I added C:\Program Files\Microsoft DirectX SDK (August 2008)\Lib\x86

3. Visual C++ Paths I added C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Lib and C:\Program Files\Microsoft Visual

Studio 8\VC\lib

Also, C:\cygwin\bin and c:\python26 directories are under executable files and moved to the bottom of the list.

Note: The instructions on this page say to use ActivePython, but the rest of the instructions say that regular

python will work also. I decided to stick with ActivePython because it will be required when I go to reinstall

Blender (I haven't re-installed Blender yet since my last backup and format, but I know in the future I will

need it). Also, the web page says to put C:\python25 but I only have C:\python26, so I used that.

Note: I forgot to add to the libraries globals the firs time around. I'm fixing that now though.

From here I went to the Microsoft Windows Builds page on the wiki.

http://wiki.secondlife.com/wiki/Microsoft_Windows_Builds

Getting other Development Tools:

Cmake, Cygwin, Python, the Windows Platform SDK and DirectX 9.0 all installed fine. I was careful to follow all

instructions, but some instructions were outdated.

Cmake: I am using CMake 2.6.4, but when the page was written the latest version was 2.6.2.

Cygwin: The install went smooth. I made sure to install patchutils, flex and bison during the install.

Python: It says that if I am using a python version newer than 2.5 I might have to change the python.cmake

file. I haven't done that yet. That might be a problem.

Windows Platform SDK: Installed smooth.

DirectX 9.0: Installed smooth.

What the heck is a PATH?

The instructions say to make sure that Cygwin, CMake and Python are in the windows "PATH". I had no idea what

this means, but the friendly nerds in my SL groups helped me find it when I got to the "Building with CMake"

section and the build started failing.

PATH is a variable in the system variables section of the Environment Variables window. You can find Enviroment

Variables in Control Panel > System > Advanced System Settings > Advanced Tab > Environment Variables button.

I scrolled down the bottom list of variables until I got to the path variable. I selected path, hit edit and

added the following string to the end of what was already in there:

C: \Python26;C:\cygwin\bin;C:\Program Files\CMake 2.6\bin

This made the full path variable look like this:

%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0

\;C:\Program Files\QuickTime\QTSystem\;C:\Python26;C:\cygwin\bin;C:\Program Files\CMake 2.6\bin

Downloading Source Code:

I downloaded the source code and extracted it all on the C drive with a path C:\Source, so each source code file

has it's own folder within Source. I have the following paths now: C:\Source\slviewer-1.23.5 C:\Source\slviewer-art-1.23.5 C:\Source\slviewer-libs-1.23.5

Proprietary Libraries:

Fmod downloaded and installed fine. I put it in the C:\Source directory, so now I have C:\Source\Fmod

Quicktime installed fine. I have it in it's default install directory, at c:\Program Files\QuickTime SDK

I also made a Library file in C:\Source, at C:\Source\Proprietary This is where I made the tree of files I will

then move to the c:\Source\slviewer-1.23.5 tree.

The first time I did this I put fmodvx.lib in lib_release and lib_debug rather than lib\release and lib\debug by

mistake. I also put QTMLClient.lib in lib_release and lib_debug instead of lib\release and lib\debug by

mistake.

I know, maybe I should have read more carefully, but I think the web page documentation would be easier to

follow if the parenthetical section had a seperate heading for "Using CMake" and for "not using CMake". To be

honest, I don't know why they include options for not using CMake, because if somebody is using this web page

they are probably, like me, a noob and don't know how to build without CMake anyway.

Building with CMake:

This is where I'm stuck now.

At first I made the mistake of going to start > run and typed "command" to get to a command prompt. This was a

mistake because "command" can not work with long file names, and I need to work with long file names to navigate

to where I need to be. I ran "cmd" instead and then everything started working right.

Then I could not figure out how to get this to work because my PATH variables were not set. "python" returned

an invalid command error. It took me all day to try to troubleshoot it on my own but and finally I found a

group that helped me out (thanks, AW Groupies!). Now python runs from a command prompt but I get errors when I try to build.

The wiki documentation says to use quotes on the build command but when I do that I get the error that what I

typed is not recognized as an internal or external command, operable progam or batch file. It tries to run when

I do it without the quotes though.

Here is the output I get now:

C:\Source\slviewer-1.23.5\linden\indra>python develop.py -G VC80 Running 'cmake -G "Visual Studio 8 2005" -DSTANDALONE:BOOL=OFF -DUNATTENDED:BOOL =OFF -DROOT_PROJECT_NAME:STRING=SecondLife "" "C:\\Source\\slviewer-1.23.5\\lind en\\indra"' in 'build-VC80' -- Check for working C compiler: cl -- Check for working C compiler: cl -- broken CMake Error at C:/Program Files/CMake 2.6/share/cmake-2.6/Modules/CMakeTestCComp iler.cmake:32 (MESSAGE):

 The C compiler "cl" is not able to compile a simple test program.

 It fails with the following output:

  Change Dir: C:/Source/slviewer-1.23.5/linden/indra/build-VC80/CMakeFiles/CMak

eTmp

 Run Build Command:C:\PROGRA~1\MICROS~4\Common7\IDE\VCExpress.exe
 CMAKE_TRY_COMPILE.sln /build Debug /project cmTryCompileExec

 Microsoft (R) Visual C++ Express Edition Version 8.0.50727.867.

 Copyright (C) Microsoft Corp 1984-2005.  All rights reserved.

 1>------ Build started: Project: cmTryCompileExec, Configuration: Debug
 Win32 ------

 1>Compiling...

 1>Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762
 for 80x86

 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"C:/Source/slviewer-1.23.5/linden/indra/build-VC80/CMakeFiles/CMakeTmp/Debu

g/cmTryCompileExec.pdb"

 /W3 /c /Zi /TC /Zm1000

 1> ".\testCCompiler.c"

 1>testCCompiler.c

 1>Compiling manifest to resources...

 1>Linking...

 1>LINK : fatal error LNK1104: cannot open file 'user32.lib'

 1>Build log was saved at
 "file://c:\Source\slviewer-1.23.5\linden\indra\build-VC80\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
 ==========

 CMake will not be able to correctly generate this project.

Call Stack (most recent call first):

 CMakeLists.txt:17 (project)

-- Configuring incomplete, errors occurred! Cleaning 'build-VC80' Error: the command 'cmake' exited with status 1

So, I see two errors in this output that bother me.

1. -- Check for working C compiler: cl -- broken CMake Error at C:/Program Files/CMake 2.6/share/cmake-2.6/Modules/CMakeTestCComp iler.cmake:32 (MESSAGE):

 The C compiler "cl" is not able to compile a simple test program.

2. 1>LINK : fatal error LNK1104: cannot open file 'user32.lib'

I checked my CMake to make sure it was configured to find Visual C++. I opened the CMake GUI and went to Tools

> Configure. I selected Visual Studio 8 2005 from the drop down and left it set to use default native compilers

and clicked Finish and got a window with the following error message: "Error in configuration process, project

files may be invalid". I clicked OK to close the error, closed the GUI and re-installed CMake from the file I

installed it from earlier. I'm still getting the same problem.

The first error above might give me a clue as to what needs to be done. After the error it says:

 It fails with the following output:

  Change Dir: C:/Source/slviewer-1.23.5/linden/indra/build-VC80/CMakeFiles/CMak

eTmp

 Run Build Command:C:\PROGRA~1\MICROS~4\Common7\IDE\VCExpress.exe
 CMAKE_TRY_COMPILE.sln /build Debug /project cmTryCompileExec

Now I need to figure out how to run build commands.

My first guess is to cd C:/Source/slviewer-1.23.5/linden/indra/build-VC80/CMakeFiles/CMakeTmp and then type

build C:\PROGRA~1\MICROS~4\Common7\IDE\VCExpress.exe and then type CMAKE_TRY_COMPILE.sln /build Debug /project

cmTryCompileExec

Lets see how this works:

C:\Source\slviewer-1.23.5\linden\indra>cd C:/Source/slviewer-1.23.5/linden/indra /build-VC80/CMakeFiles/CMakeTmp The system cannot find the path specified.

The file can not be found because at the end of the failed build CMake deleted the VC80 file, as can be seen

here:

Cleaning 'build-VC80'

So I tried just running the build command from where I am:

C:\Source\slviewer-1.23.5\linden\indra>build C:\PROGRA~1\MICROS~4\Common7\IDE\VCExpress.exe 'build' is not recognized as an internal or external command, operable program or batch file.

That didn't go so well.

Lets just run the executable and see what happens. It will probably just open up Visual C++ for me.

I was right, it just opened up Visual C++. Maybe the build will work when I try to build with Visual C++

running in the background.

It almost worked! I have python and Visual C++ running in the background ATM, and when I tried to build I got

the following output:

C:\Source\slviewer-1.23.5\linden\indra>python develop.py -G VC80 Running 'cmake -G "Visual Studio 8 2005" -DSTANDALONE:BOOL=OFF -DUNATTENDED:BOOL =OFF -DROOT_PROJECT_NAME:STRING=SecondLife "" "C:\\Source\\slviewer-1.23.5\\lind en\\indra"' in 'build-VC80' -- Check for working C compiler: cl -- Check for working C compiler: cl -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: cl -- Check for working CXX compiler: cl -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done install.py:67: DeprecationWarning: the md5 module is deprecated; use hashlib ins tead

 import md5