Compiling

by C_olin on 03/11/2004 00:47, 101 messages, last message: 04/04/2006 20:25, 57552 views, last view: 06/26/2024 04:03

I'm no noob to VC++ 6.0... but I have not gotten Cube to compile correctly!

I put all of the includes and libs where they are supposed to be in the vc++ folder.

And added the right linking stuff... but I still get unresolved externals.

And why doesn't it include a VC++ workspace?

Does anyone have project/workspace project files they are wiling to send to me?

This would help out me, and a lot of other poeple... thanks!

   Board Index   

#35: ..

by ChesterHQ on 04/10/2004 10:54

http://chesterhq.quarin.net/mingw.jpg

reply to this message

#36: ..

by ChesterHQ on 04/10/2004 10:58

oh wait i just set the path still doesnt work look http://chesterhq.quarin.net/mingw2.jpg

reply to this message

#37: Re: ..

by pushplay on 04/10/2004 20:08, refers to #36

No problemo. Once the path is set you run mingw32-make from the src dir. It will know to look for Makefile in the current dir.

reply to this message

#38: ..

by ChesterHQ on 04/11/2004 23:28

ok that worked now i got this..

http://chesterhq.quarin.net/err2.jpg

it just has to work.. tell me what did i do now?

reply to this message

#39: Re: ..

by pushplay on 04/12/2004 00:24, refers to #38

I bet ../../bin doesn't exist. It wants to make the exe in E:\MinGW\bin\bin.

reply to this message

#40: ..

by ChesterHQ on 04/12/2004 01:08

yes!it works.. thank you so much!

reply to this message

#41: Re: ..

by Thalion on 04/12/2004 05:05, refers to #38

You're supposed to unpack the archive file with source code into the Cube directory and build it from there!

reply to this message

#42: ..

by ChesterHQ on 04/12/2004 11:38

well.. it works like this aswell, i just copy the exe to the bin dir everytime i compile

reply to this message

#43: VC++

by pushplay on 04/19/2004 05:49

Just released for free is a new set of compile tools for Windows:
http://msdn.microsoft.com/visualc/vctoolkit2003/
I haven't tried it yet myself but I intend to.

reply to this message

#44: ..

by >driAn<. on 04/26/2004 19:59

Hi,
i tryed to compile cube under linux:
it works fine (except some warnings).
But when I try to run it, it gives me following error:
Fatal signal: Segmentation Fault (SDL Parachute Deployed)

But the original binaries are working fine! After that, i got the newest sdl libraries, but that doesnt help..

I read this message means that the program tries to read/write in a 'not allowed' memory :/

What can i do? May there be a problem with a pointer?

thx

reply to this message

#45: Re: ..

by pushplay on 04/26/2004 20:46, refers to #44

Are you sure you're running it from the right location? ie: cube/bin?

reply to this message

#46: ..

by >driAn<. on 04/26/2004 20:54

i run it like the original binarie...
cd in the cube directory then
./bin_unix/cube_client

here the shell output:

drian@linux:~/stuff/cube> ./bin_unix/cube_client
init: sdl
init: net
init: world
game mode is ffa/default
init: video: sdl
init: video: mode
init: video: misc
init: gl
Fatal signal: Segmentation Fault (SDL Parachute Deployed)
drian@linux:~/stuff/cube>

reply to this message

#47: ..

by >driAn<. on 04/26/2004 21:41

i put the make-output (cause of the warnings) and the compiled binarie in a zip file:
http://kiney.homelinux.org/sambaweb/ftp/drian/error.zip

please check if it runs on your pc..
thx

reply to this message

#48: Re: ..

by D.plomat on 04/27/2004 10:11, refers to #47

Those warnings are harmless, i also have them on my system.
You should also try
killall esd ; killall artsd
before starting Cube

reply to this message

#49: ..

by >driAn<. on 04/27/2004 11:30

It also doesnt work with the killall commands...

D.plomat: Runs my compiled cube on your machine?

reply to this message

#50: ..

by >driAn<. on 04/27/2004 12:00

In the main.cpp i added SDL_INIT_NOPARACHUTE
to the SDL_Init() function and compiled it again.
It ignores now this error. I started cube but then it crashes fully cause of an 'memory write error' or however you call that in english...

reply to this message

#51: Re: ..

by D.plomat on 04/28/2004 01:15, refers to #49

Same thing on my machine.

Strange thing with the binary is that with ldd it gives the same output as original cube binary, except that it doesn't link to /usr/lib/libGL.so.1
As the binary is a bit larger on an amount little less than /usr/lib/libGL.so.1, would it be that libGL has been statically linked into the binary?
This is very probable, as strings drian_cube | grep gl | wc returns ~900 lines on your binary, VS only 74 for original Cube binary

maybe this is related, as it seems to crash just after GL initialisation. The strange thing is that this leads to an error physically not in libGL but in libSDL.

You used original source, unmodified Makefile and compiled with a vanilla 'make' in src dir, right?

You should try to check if other GL apps you compile yourself on this machine are compiling and working correctly.

reply to this message

#52: ..

by >driAn<. on 04/28/2004 13:31

Yes, I compiled the original source, unmodified.

Here a gl-screensaver i compiled and started without problems:

http://freshmeat.net/projects/maniwheel/

That is "an other GL app", isnt it?

reply to this message

#53: Re: ..

by D.plomat on 04/29/2004 11:14, refers to #52

Yes.

You should try a ldd on it to see if it is dynamically linked to libGL

reply to this message

#54: ..

by -=:gandalf:=- on 05/02/2004 09:42

I just tried to compile cube under Linux, but there is one problem:
/usr/bin/ld: cannot find -lGLU
collect2: ld returned 1 exit status
make: *** [client] Fehler 1

how can I fix this?
I think there ist just a missing libraray, but I don\'t know wich one, the prebuild binaries are running fine.

reply to this message

   Board Index