Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
179 user(s) are online (155 user(s) are browsing Forums)

Members: 0
Guests: 179

more...

Support us!
Donate

Headlines
Recent files - OS4Depot - Your one stop for AmigaOS4 files

 
Jump to the bottom of the page Bottom    View previous topic Previous Topic    View next topic Next Topic

  Register To Post  

« 1 2 3 (4) 5 »
salass00
Re: Making WarZone 2100 ..
Posted on: 2010/8/30 5:47    #61
Just can't stay away
Just can't stay away


See User information
@samo79

Looks like perl OS4 version is a little too old (v5.8.5.06):
perl.tar.bz2
You could try just disabling/removing the version check in the configure script though. Maybe it will work well enough then with this 5.8 version.

As for the other message just add "--with-distributor=samo79" or something like that to the ./configure line.
Go to top
samo79
Re: Making WarZone 2100 ..
Posted on: 2010/8/30 6:47    #62
Home away from home
Home away from home


See User information
@salass00

It's ok now !

Finally i use this command:

Quote:
./configure --with-distributor=samo79 --disable-dependency-tracking --bindir=/SDK/Local/C --prefix=/SDK/Local --libdir=/SDK/Local/newlib/lib LIBS="-lauto -lunix" "CC=gcc -mcrt=newlib -use-dynld" "CXX=g++ -mcrt=newlib -use-dynld"


Regarding Perl I've found this in configure file:

Quote:
if test -n "$PERL"; then :
ax_perl_version="5.10"


So I modify it in:

version="5.8"

Now i have this output (not complete in this post)

SNIP
Quote:
checking whether to use NLS... no
checking for pkg-config... /Cygnix/CygnixPPC/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for pkg-config >= 0.9... found 0.19, ok
checking whether to build NSIS installer... no
checking whether to compile in debug mode... no
checking whether the C compiler accepts the -Werror -Wno-switch flag... yes
checking whether the C compiler accepts the -Werror -Wno-enum-compare flag... no
checking for SDL... yes
checking for PNG... yes
checking for THEORA... yes
checking for OPENAL... yes
checking for OGGVORBIS... yes
checking for GLee... gnome-config: Comando sconosciuto
gnome-config fallito con codice 10
no
checking for GLee.h...
checking for GLee.h with -I/usr/local/include/GL... no
checking for GLee.h with -I/usr/include/GL... no
checking GLee.h usability... no
checking GLee.h presence... no
checking for GLee.h... no
configure: Using integrated GLee
checking for nearbyint in -lm... yes
checking Xm/Xm.h usability... no
checking Xm/Xm.h presence... no
checking for Xm/Xm.h... no
checking for XmCreateErrorDialog in -lXm... no
checking popt.h usability... yes
checking popt.h presence... yes
checking for popt.h... yes
checking for poptGetContext in -lpopt... yes
configure: not updating unwritable cache /dev/null
configure: creating ./config.status
config.status: creating Makefile
config.status: creating po/Makefile.in
config.status: creating doc/Makefile
config.status: creating build_tools/Makefile
config.status: creating build_tools/autorevision/Makefile
config.status: creating icons/Makefile
config.status: creating data/Makefile
config.status: creating data/mods/Makefile
config.status: creating data/mods/multiplay/Makefile
config.status: creating data/music/Makefile
config.status: creating pkg/Makefile
config.status: creating pkg/nsis/Makefile
config.status: creating win32/Makefile
config.status: creating lib/Makefile
config.status: creating lib/framework/Makefile
config.status: creating lib/exceptionhandler/Makefile
config.status: creating lib/gamelib/Makefile
config.status: creating lib/iniparser/Makefile
config.status: creating lib/ivis_opengl/Makefile
config.status: creating lib/ivis_common/Makefile
config.status: creating lib/netplay/Makefile
config.status: creating lib/netplay/miniupnpc/Makefile
config.status: creating lib/script/Makefile
config.status: creating lib/sequence/Makefile
config.status: creating lib/sound/Makefile
config.status: creating lib/widget/Makefile
config.status: creating src/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing po-directories commands
config.status: creating po/POTFILES
config.status: creating po/Makefile
/Work/SDK/Progetti/warzone2100-2.3.4>

/SNIP

Can i try to gmake from makefile now ?

Go to top
salass00
Re: Making WarZone 2100 ..
Posted on: 2010/8/30 7:03    #63
Just can't stay away
Just can't stay away


See User information
@samo79

Sure, go ahead .
Go to top
samo79
Re: Making WarZone 2100 ..
Posted on: 2010/8/30 7:44    #64
Home away from home
Home away from home


See User information
@salass00

First problem :-/

Quote:
/Work/SDK/Progetti/warzone2100-2.3.4> gmake
/SDK/C/gmake all-recursive
gmake[1]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4'
Making all in build_tools
gmake[2]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4/build_tools'
Making all in autorevision
gmake[3]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4/build_tools/autorevision'
g++ -mcrt=newlib -use-dynld -DHAVE_CONFIG_H -I. -I../.. -g -O2 -c -o autorevision.o autorevision.cpp
g++ -mcrt=newlib -use-dynld -g -O2 -rdynamic -o autorevision autorevision.o -lauto -lunix
./autorevision +cstr -v ../.. ../../src/autorevision.h
svn: Path '../..' ends in '..', which is unsupported for this operation
svn fallito con codice 20
git: Comando sconosciuto
git fallito con codice 10
git: Comando sconosciuto
git fallito con codice 10
Warning: could not open input file.
This does not seem to be a revision controlled project.
Warning: could not open input file.
This does not seem to be a revision controlled project.
Error: failed retrieving version information.
Warning: using 0 as revision.
gmake[3]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4/build_tools/autorevision'
gmake[3]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4/build_tools'
gmake[3]: Nothing to be done for `all-am'.
gmake[3]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4/build_tools'
gmake[2]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4/build_tools'
Making all in win32
gmake[2]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4/win32'
gmake[2]: Nothing to be done for `all'.
gmake[2]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4/win32'
Making all in lib
gmake[2]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4/lib'
Making all in framework
gmake[3]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4/lib/framework'
/SDK/C/gmake all-am
gmake[4]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4/lib/framework'
gcc -mcrt=newlib -use-dynld -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -DYY_NO_INPUT -I/SDK/local/common/include/SDL -DNDEBUG -DWZ_DATADIR="\"/SDK/Local/share/warzone2100\"" -DLOCALEDIR="\"/SDK/Local/share/locale\"" -I../.. -g -Wall -Wwrite-strings -c resource_lexer.lex.c
In file included from ../../lib/framework/frame.h:26,
from resource_lexer.l:26:
../../lib/framework/wzglobal.h:162:4: error: #error "Warzone has not been tested on this OS. Please contact warzone-dev@gna.org"
gmake[4]: *** [resource_lexer.lex.o] Error 1
gmake[4]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4/lib/framework'
gmake[3]: *** [all] Error 2
gmake[3]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4/lib/framework'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4/lib'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4'
bin:gmake: *** [all] Error 2
/Work/SDK/Progetti/warzone2100-2.3.4>


:-O

Warzone has not been tested on this OS. Please contact warzone-dev@gna.org

????
Go to top
kas1e
Re: Making WarZone 2100 ..
Posted on: 2010/8/30 7:47    #65
Home away from home
Home away from home


See User information
@samo79

You should run abc-shell before doing all the stuff (can be ok for doing makefiles from amiga-dos prompt , but gmake offten want unix-shell).

So, type in dos-prompt: "sh" (it will spawn for you unix-kind shell), and then, gmake.
Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
samo79
Re: Making WarZone 2100 ..
Posted on: 2010/8/30 7:53    #66
Home away from home
Home away from home


See User information
@kas1e

Mmm i'm already into sh, I used the same shell opened for give commands in configure

Example:

Quote:
Processo: Shell 8
8.AmigaOS4:> Work:SDK/Progetti/warzone2100-2.3.4/
8.Work:SDK/Progetti/warzone2100-2.3.4> sh
/Work/SDK/Progetti/warzone2100-2.3.4> gmake
/SDK/C/gmake all-recursive
gmake[1]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4'
Making all in build_tools
gmake[2]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4/build_tools'
Making all in autorevision
gmake[3]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4/build_tools/autorevision'
./autorevision +cstr -v ../.. ../../src/autorevision.h
svn: Path '../..' ends in '..', which is unsupported for this operation
svn fallito con codice 20
git: Comando sconosciuto
git fallito con codice 10
git: Comando sconosciuto
git fallito con codice 10
Warning: could not open input file.
This does not seem to be a revision controlled project.
Warning: could not open input file.
This does not seem to be a revision controlled project.
Error: failed retrieving version information.
Warning: using 0 as revision.
Revision unchanged (0). Skipping.
old = "0"; new = "0"
gmake[3]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4/build_tools/autorevision'
gmake[3]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4/build_tools'
gmake[3]: Nothing to be done for `all-am'.
gmake[3]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4/build_tools'
gmake[2]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4/build_tools'
Making all in win32
gmake[2]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4/win32'
gmake[2]: Nothing to be done for `all'.
gmake[2]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4/win32'
Making all in lib
gmake[2]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4/lib'
Making all in framework
gmake[3]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4/lib/framework'
/SDK/C/gmake all-am
gmake[4]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4/lib/framework'
gcc -mcrt=newlib -use-dynld -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -DYY_NO_INPUT -I/SDK/local/common/include/SDL -DNDEBUG -DWZ_DATADIR="\"/SDK/Local/share/warzone2100\"" -DLOCALEDIR="\"/SDK/Local/share/locale\"" -I../.. -g -Wall -Wwrite-strings -c resource_lexer.lex.c
In file included from ../../lib/framework/frame.h:26,
from resource_lexer.l:26:
../../lib/framework/wzglobal.h:162:4: error: #error "Warzone has not been tested on this OS. Please contact warzone-dev@gna.org"
gmake[4]: *** [resource_lexer.lex.o] Error 1
gmake[4]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4/lib/framework'
gmake[3]: *** [all] Error 2
gmake[3]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4/lib/framework'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4/lib'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4'
bin:gmake: *** [all] Error 2
/Work/SDK/Progetti/warzone2100-2.3.4>

Go to top
kas1e
Re: Making WarZone 2100 ..
Posted on: 2010/8/30 8:08    #67
Home away from home
Home away from home


See User information
@samo79

As i see, it tryes to use some crappo file called "autorevision", which call in end SVN or GIT command (what mean, that it tryes to connnect to repository of warzone, for the latest sources or for some other checking-not-needit-crap).

So, maybe you can specifiy to ./configure something like "disable autorevision" param, or, if nothing like that will be in help outout of configure, then, just found that file (autorevision), and delete everything inside.

PS. Try also to do "gmake --help", maybe you can specify something like "gmake game_only" or kind (to avoid builing of other tools)
Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Joeled
Re: Making WarZone 2100 ..
Posted on: 2010/8/30 8:35    #68
Quite a regular
Quite a regular


See User information
@samo79
Nice to see you making progress

Kas1e
Any progress on Egoboo? Did you find any solutions?
Go to top
kas1e
Re: Making WarZone 2100 ..
Posted on: 2010/8/30 9:39    #69
Home away from home
Home away from home


See User information
@Joeled
Right now works on it. It have heavy errors with opengl (minigl), but what cause a reassons - dunno for now. I also get some help from Egoboo authors (on their forum), and right now trying to delete everything, build from scratch with debug information, and check what is happenes. I also send a mail to Hanz with some question about some fucntions which are not in the MiniGL (but which Egoboo are used for). Before i just comment out these fucntions, so, very possible that all the problems because of that.
Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
salass00
Re: Making WarZone 2100 ..
Posted on: 2010/8/30 10:27    #70
Just can't stay away
Just can't stay away


See User information
@samo79

If you could post the contents of that "wzglobal.h" then we can probably figure out how to fix it. In best case scenario it just needs to check for an additional define.
Go to top
samo79
Re: Making WarZone 2100 ..
Posted on: 2010/8/30 10:41    #71
Home away from home
Home away from home


See User information
@salass00

Sure here is it:

http://www.qimmagine.it/owb/wzglobal.h
Go to top
kas1e
Re: Making WarZone 2100 ..
Posted on: 2010/8/30 10:50    #72
Home away from home
Home away from home


See User information
What i found in that file:

Quote:

The window system, must be one of: (WZ_WS_x)

MACX - Mac OS X
WIN32 - Windows
X11 - X Window System
QNX - QNX


So, for window system there is support of only 4 oses, and for unix (which we can use), there is x11 crap. Other stuff are easy to fix, but dunno what we will do with that x11 crap.
Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
samo79
Re: Making WarZone 2100 ..
Posted on: 2010/8/30 11:21    #73
Home away from home
Home away from home


See User information
@kas1e

Yep it's strange that a game use X11, for what then ? ..

The rest as Fredrik say are defines, if we can modify it, i'm plane to send the diff to the team, so AmigaOS will be supported by default in future release

Go to top
kas1e
Re: Making WarZone 2100 ..
Posted on: 2010/8/30 11:27    #74
Home away from home
Home away from home


See User information
@samo79
Before sending any files, we need to build working game :)

Related to X11, i think, that when they build Unix version they use not SDL+GL for window managment, but sucking X11. Dunno how heavy and deep they come with it in code ..

I am sure that it will be not so easy like just changing defines in that file. But our hope, that there is only few x11 dependences (but maybe not). X11 can be used for handling keys, windows, and others, which can be rewrited of course, but will be not so easy like just fixing of 1 define.
Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
kas1e
Re: Making WarZone 2100 ..
Posted on: 2010/8/30 11:31    #75
Home away from home
Home away from home


See User information
@samo79
Try my modified file here

I just add there these strings:
Quote:

#if defined(__amigaos4__)
#define WZ_OS_UNIX
#endif /* WZ_OS_* */


That mean, that for aos4 will be used unix code.

Lets try to build with it, and will see what it will say about win-managment.
Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
samo79
Re: Making WarZone 2100 ..
Posted on: 2010/8/30 11:36    #76
Home away from home
Home away from home


See User information
@kas1e

Quote:
Before sending any files, we need to build working game :)


Off course

I try with your modificated file but it's the same:

/Work/SDK/Progetti/warzone2100-2.3.4> gmake
/SDK/C/gmake all-recursive
gmake[1]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4'
Making all in build_tools
gmake[2]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4/build_tools'
Making all in autorevision
gmake[3]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4/build_tools/autorevision'
./autorevision +cstr -v ../.. ../../src/autorevision.h
svn: Path '../..' ends in '..', which is unsupported for this operation
svn fallito con codice 20
git: Comando sconosciuto
git fallito con codice 10
git: Comando sconosciuto
git fallito con codice 10
Warning: could not open input file.
This does not seem to be a revision controlled project.
Warning: could not open input file.
This does not seem to be a revision controlled project.
Error: failed retrieving version information.
Warning: using 0 as revision.
Revision unchanged (0). Skipping.
old = "0"; new = "0"
gmake[3]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4/build_tools/autorevision'
gmake[3]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4/build_tools'
gmake[3]: Nothing to be done for `all-am'.
gmake[3]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4/build_tools'
gmake[2]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4/build_tools'
Making all in win32
gmake[2]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4/win32'
gmake[2]: Nothing to be done for `all'.
gmake[2]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4/win32'
Making all in lib
gmake[2]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4/lib'
Making all in framework
gmake[3]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4/lib/framework'
/SDK/C/gmake all-am
gmake[4]: Entering directory `/Work/SDK/Progetti/warzone2100-2.3.4/lib/framework'
gcc -mcrt=newlib -use-dynld -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -DYY_NO_INPUT -I/SDK/local/common/include/SDL -DNDEBUG -DWZ_DATADIR="\"/SDK/Local/share/warzone2100\"" -DLOCALEDIR="\"/SDK/Local/share/locale\"" -I../.. -g -Wall -Wwrite-strings -c resource_lexer.lex.c
In file included from ../../lib/framework/frame.h:26,
from resource_lexer.l:26:
../../lib/framework/wzglobal.h:162:4: error: #error "Warzone has not been tested on this OS. Please contact warzone-dev@gna.org"
gmake[4]: *** [resource_lexer.lex.o] Error 1
gmake[4]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4/lib/framework'
gmake[3]: *** [all] Error 2
gmake[3]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4/lib/framework'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4/lib'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4'
bin:gmake: *** [all] Error 2
/Work/SDK/Progetti/warzone2100-2.3.4> -
Go to top
salass00
Re: Making WarZone 2100 ..
Posted on: 2010/8/30 11:43    #77
Just can't stay away
Just can't stay away


See User information
@samo79

I would modify it this way instead:
wzglobal.h

With these changes you won't get that stupid x11 window system define which you get stuck with if you define WZ_OS_UNIX. You might have to do some more changes in the long run but IMO it's worth it.
Go to top
kas1e
Re: Making WarZone 2100 ..
Posted on: 2010/8/30 11:47    #78
Home away from home
Home away from home


See User information
@salass00

But imho, if there will be no UNIX defines, then, there will be no right includes, and some unix dependences (like posix fucntions and alt) .
Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
samo79
Re: Making WarZone 2100 ..
Posted on: 2010/8/30 11:51    #79
Home away from home
Home away from home


See User information
@salass00

Infact now we have a step forward

Quote:
exceptionhandler.c:149: error: array type has incomplete element type
exceptionhandler.c: In function 'setFatalSignalHandler':
exceptionhandler.c:360: error: storage size of 'new_handler' isn't known
exceptionhandler.c:362: warning: left-hand operand of comma expression has no effect
exceptionhandler.c:362: warning: statement with no effect
exceptionhandler.c:370: warning: implicit declaration of function 'sigaction'
exceptionhandler.c:360: warning: unused variable 'new_handler'
exceptionhandler.c: In function 'execGdb':
exceptionhandler.c:461: warning: implicit declaration of function 'pipe'
exceptionhandler.c:472: warning: implicit declaration of function 'fork'
exceptionhandler.c:510: warning: implicit declaration of function 'execve'
gmake[3]: *** [exceptionhandler.o] Error 1
gmake[3]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4/lib/exceptionhandler'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4/lib'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/Work/SDK/Progetti/warzone2100-2.3.4'
bin:gmake: *** [all] Error 2
/Work/SDK/Progetti/warzone2100-2.3.4>
Go to top
kas1e
Re: Making WarZone 2100 ..
Posted on: 2010/8/30 12:17    #80
Home away from home
Home away from home


See User information
line 149:
Quote:

static struct sigaction oldAction[NSIG];


Full part of code related to that line:
Quote:

#ifdef WZ_OS_MAC
static struct sigaction oldAction[32];
#elif defined(_NSIG)
static struct sigaction oldAction[_NSIG];
#else
static struct sigaction oldAction[NSIG];
#endif


Line 360:
Quote:

struct sigaction new_handler;


Line362:
Quote:

sigemptyset(&new_handler.sa_mask);


And so on, all about the same.
Join us to improve dopus5!
AmigaOS4 on youtube
Go to top

  Register To Post
« 1 2 3 (4) 5 »

 
Jump to the top of the page Top    View previous topic Previous Topic    View next topic Next Topic




Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )




Powered by XOOPS 2.0 © 2001-2024 The XOOPS Project