Lots of errors trying to build Oolite from source

News and discussion of the PC port of Oolite.

Moderators: winston, another_commander

Post Reply
User avatar
Griff
Oolite 2 Art Director
Oolite 2 Art Director
Posts: 2483
Joined: Fri Jul 14, 2006 12:29 pm
Location: Probably hugging his Air Fryer

Lots of errors trying to build Oolite from source

Post by Griff »

I've been trying to build Oolite using the guide on the wiki (the 'updated 19 May 2008' one), everything goes really well up until step 10.4
after i type make and presws enter, a few of the first tasks seem to complete ok, then there's a massive flood of errors about 30 screens full - so many that i can't scroll back up to the top of the list to find out what first went wrong!
i'm not sure how to copy and paste text out of the GNUStep window, so i've attached a screen grab of the last few errors, anybody know what i've done wrong?
Image
around about step 10 on the wiki there's an extra bit of text from 'Ean' saying "I had to add /Local/include to the include search path", i don't know how to do that, maybe that's the bit i'm missing?
I haven't installed gnustep to drive C: either, i've got a Vista/XP dual boot system and C: is my vista partition, but i'm using the XP partition which is drive E: so that's where i installed gnustep to.
Top
User avatar
Micha
Commodore
Commodore
Posts: 815
Joined: Tue Sep 02, 2008 2:01 pm
Location: London, UK
Contact:
Contact Micha

Post by Micha »

Have you built the Spidermonkey dependency? Also, which version of Oolite are you building?
The glass is twice as big as it needs to be.
Top
another_commander
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
Posts: 6683
Joined: Wed Feb 28, 2007 7:54 am

Post by another_commander »

We really need to have a look at the first errors you get rather than the last ones. But it looks like it is missing some include directory indeed. To see the first errors, try to redirect make's output with something like

Code: Select all

make > /c/myerrorlog.txt
To copy text from Msys to Notepad: Click and drag mouse over the text you want to copy in the Msys window, go to the Notepad window and right-click -> paste. Job done.
Top
User avatar
Griff
Oolite 2 Art Director
Oolite 2 Art Director
Posts: 2483
Joined: Fri Jul 14, 2006 12:29 pm
Location: Probably hugging his Air Fryer

Post by Griff »

is there a log file? sorry guys, i'm totally clueless at this.
edit: duh, sorry A_C i didn't notice your post about how to make the logfile, i'll have a go at that now.

Hmm, the log file only recorded the stuff that happened OK, it seems to stop when all the error start, this is what it logged:
Making all for objc_program oolite...
Compiling file src/Core/legacy_random.c ...
Compiling file src/BSDCompat/strlcpy.c ...
Compiling file src/Core/Debug/OOTCPStreamDecoder.c ...
Compiling file src/Core/OOCocoa.m ...
Compiling file src/SDL/Comparison.m ...
Compiling file src/Core/AI.m ...
Last edited by Griff on Tue Nov 25, 2008 10:33 pm, edited 1 time in total.
Top
User avatar
JensAyton
Grand Admiral Emeritus
Grand Admiral Emeritus
Posts: 6657
Joined: Sat Apr 02, 2005 2:43 pm
Location: Sweden
Contact:
Contact JensAyton

Post by JensAyton »

Also, to get all the text spewed by make:

Code: Select all

make > somefile.txt 2>&1
Top
User avatar
Griff
Oolite 2 Art Director
Oolite 2 Art Director
Posts: 2483
Joined: Fri Jul 14, 2006 12:29 pm
Location: Probably hugging his Air Fryer

Post by Griff »

ah ha, here's the start bit of the log:

Code: Select all

Making all for objc_program oolite... 
Compiling file src/Core/legacy_random.c ...
 Compiling file src/BSDCompat/strlcpy.c ...
 Compiling file src/Core/Debug/OOTCPStreamDecoder.c ...
 Compiling file src/Core/OOCocoa.m ...
 Compiling file src/SDL/Comparison.m ...
 Compiling file src/Core/AI.m ...
In file included from src/Core/ResourceManager.h:28,
                 from src/Core/AI.m:26:
src/Core/OOOpenGL.h:57:24: warning: SDL_opengl.h: No such file or directory
In file included from src/Core/OOOpenGL.h:60,
                 from src/Core/ResourceManager.h:28,
                 from src/Core/AI.m:26:
deps/Windows-x86-deps/include/GL/glext.h:3119: error: syntax error before "red"
deps/Windows-x86-deps/include/GL/glext.h:3120: error: syntax error before "mode"
deps/Windows-x86-deps/include/GL/glext.h:3121: error: syntax error before "mode"
deps/Windows-x86-deps/include/GL/glext.h:3122: error: syntax error before "target"
deps/Windows-x86-deps/include/GL/glext.h:3123: error: syntax error before "target"
deps/Windows-x86-deps/include/GL/glext.h:3124: error: syntax error before "target"
deps/Windows-x86-deps/include/GL/glext.h:3125: error: syntax error before "target"
deps/Windows-x86-deps/include/GL/glext.h:3126: error: syntax error before "target"
deps/Windows-x86-deps/include/GL/glext.h:3127: error: syntax error before "target"
deps/Windows-x86-deps/include/GL/glext.h:3128: error: syntax error before "target"
deps/Windows-x86-deps/include/GL/glext.h:3129: error: syntax error before "target"
deps/Windows-x86-deps/include/GL/glext.h:3130: error: syntax error before "target"
deps/Windows-x86-deps/include/GL/glext.h:3131: error: syntax error before "target"
deps/Windows-x86-deps/include/GL/glext.h:3132: error: syntax error before "target"
deps/Windows-x86-deps/include/GL/glext.h:3133: error: syntax error before "target"
deps/Windows-x86-deps/include/GL/glext.h:3134: error: syntax error before "target"
deps/Windows-x86-deps/include/GL/glext.h:3135: error: syntax error before "target"
deps/Windows-x86-deps/include/GL/glext.h:3136: error: syntax error before "target"
deps/Windows-x86-deps/include/GL/glext.h:3137: error: syntax error before "target"
deps/Windows-x86-deps/include/GL/glext.h:3138: error: syntax error before "target"
for the full horror, i've uploaded the entire logfile here (160KB's worth!)
http://www.box.net/shared/zv9ybyuec9
Last edited by Griff on Tue Nov 25, 2008 10:42 pm, edited 1 time in total.
Top
another_commander
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
Posts: 6683
Joined: Wed Feb 28, 2007 7:54 am

Post by another_commander »

And one more detail: To add an include directory in the mix, open GNUmakefile with a text editor, go to the line that starts with ADDITIONAL_INCLUDE_DIRS at the top of the file and add your directory at the end of that line using -I/Local/include. It should look something like this:

Code: Select all

ADDITIONAL_INCLUDE_DIRS = -Ideps/Windows-x86-deps/include -Isrc/SDL -Isrc/Core -Isrc/BSDCompat -Isrc/Core/Scripting -Isrc/Core/Materials -Isrc/Core/Entities -Isrc/Core/OXPVerifier -Isrc/Core/Debug -I/Local/include
If you cannot get it to work, tomorrow I will upload a minimal working development environment for Windows, that you can basically copy on your system and build.

Edit: Hmm. Looking at the error log, it looks like SDL has not been installed correctly. Have you unzipped the Local_[date].zip file using the Extract button or did you just drag and drop files? It is important that the directory structure of the file is maintained when it gets unzipped. Alternatively, try adding that /Local/include dir.
Top
User avatar
Griff
Oolite 2 Art Director
Oolite 2 Art Director
Posts: 2483
Joined: Fri Jul 14, 2006 12:29 pm
Location: Probably hugging his Air Fryer

Post by Griff »

ah, i think i opened the zip file then dragged all the folders out of it and into the GNUstep\Local folder, i just checked and it looks like it did preserve the directory structure.
Oh, i should have mentioned that GNUStep is installed on drive E: on my PC, i've got my pc set up with Windows Vista on drive C: and Windows XP on Drive E: i'm not too keen on Vista so i try and stay in Windows XP as much as possible and this is where i'm installing GNUstep to.

I've added the Local\include to the line in the GNUmakefile, it looks like this:

Code: Select all

ADDITIONAL_INCLUDE_DIRS = -Ideps/Windows-x86-deps/include -Isrc/SDL -Isrc/Core -Isrc/BSDCompat -Isrc/Core/Scripting -Isrc/Core/Materials -Isrc/Core/Entities -Isrc/Core/OXPVerifier -Isrc/Core/Debug -I/Local/include
have i got that right? it was supposed to be an I and not my drive letter E?
Top
another_commander
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
Posts: 6683
Joined: Wed Feb 28, 2007 7:54 am

Post by another_commander »

Yes, it is the -I compiler switch, which instructs it to use the directory name that follows as a standard include files folder.
Top
User avatar
Griff
Oolite 2 Art Director
Oolite 2 Art Director
Posts: 2483
Joined: Fri Jul 14, 2006 12:29 pm
Location: Probably hugging his Air Fryer

Post by Griff »

I couldn't get this to work in the end, there's no need to go to the trouble of uploading a minimal working enviroment A_C, it's very kind of you to offer, i just fancied having an early peek at the normal mapping stuff but there's no harm in me waiting for it to come out in a test release - it does look really exciting though!
Top
User avatar
Micha
Commodore
Commodore
Posts: 815
Joined: Tue Sep 02, 2008 2:01 pm
Location: London, UK
Contact:
Contact Micha

Post by Micha »

I wonder if it'd be worthwhile to make a single NSIS installer for the Oolite development environment, incorporating everything at the correct versions and whatnot.

As to your issue, Griff, I can see about building you a binary if all you want is a preview.
The glass is twice as big as it needs to be.
Top
User avatar
Griff
Oolite 2 Art Director
Oolite 2 Art Director
Posts: 2483
Joined: Fri Jul 14, 2006 12:29 pm
Location: Probably hugging his Air Fryer

Post by Griff »

oh wow, that would be cool, it's not a lot of work though is it Micha? If it is please don't put yourself out, i'm just being nosey about the normal mapping stuff!
Top
another_commander
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
Posts: 6683
Joined: Wed Feb 28, 2007 7:54 am

Post by another_commander »

I have already took the liberty of emailing Griff a test binary of the latest SVN. And I fully agree about the installer for the dev environment. It should be completely separate to the installer for the actual game, though.
Top
User avatar
Griff
Oolite 2 Art Director
Oolite 2 Art Director
Posts: 2483
Joined: Fri Jul 14, 2006 12:29 pm
Location: Probably hugging his Air Fryer

Post by Griff »

thank you A_C, i just logged into my email account and spotted the files!

Thanks everyone for your help trying to get the source built on my home pc, sadly it didn't work, but at least i've typed some crazy new symbols on the keyboard for the first time such as this one ~ what's that all about? i was expecting someone to say at one point , you've got to grep rep the tarball good buddy 10-4 over and out and send me into a flap, die hard windows user see, i can only point and click on pictures!
Top
User avatar
Micha
Commodore
Commodore
Posts: 815
Joined: Tue Sep 02, 2008 2:01 pm
Location: London, UK
Contact:
Contact Micha

Post by Micha »

@griff: once the dev environment is set up, building a binary only takes a few minutes, no sweat. Looks like a_c beat me to it though :)

@a_c: I haven't had nearly as much spare time the last few weeks as I would have liked. Still have a few more important things to tick off but I can see about getting a Windows Dev-Environment Installer going. Another (better?) solution might be to build daily/weekly snapshots for the people interested in trying the latest features, especially the OXP coders?
(OT) Noticed it's not all that trivial for Mac OSX either - there are a couple of additional packages which need installing to get Oolite compiled there too.
The glass is twice as big as it needs to be.
Top
Post Reply

Return to “Oolite-PC”