Page 2 of 3

Posted: Thu Feb 12, 2009 3:37 pm
by Rookie One.pl
Nope, you got it all wrong. Open MSYS and do this.

Code: Select all

cd /path/to/wherever/you/have/the/source/code
make
That's all you have to type in the console.

Posted: Thu Feb 12, 2009 4:25 pm
by Aprop

Code: Select all

cd c:/om/

Code: Select all

makefile
Aprop wrote:

Code: Select all

c:/o...... line7: shell: command not found
c:/o...... line9: shell: command not found
c:/o...... line11: syntax error near unexpected token '$(COMPILE PLATFORM).sunos'
c:/o...... line11 : ifeq ($(COMPILE_PLATFORM),sunos)' 

Maybe i have wrong mingw? Or some mingw files are missed?

Posted: Thu Feb 12, 2009 10:28 pm
by Rookie One.pl
NOT makefile, make! Just make on its own!

Posted: Fri Feb 13, 2009 1:55 pm
by Aprop
Tried,

Code: Select all

cd c:/om/

Code: Select all

make

Code: Select all

make
make[1]: Entering directory '/c/om'

Bulding openmohaa in build/relase_ming32-x86
PLATFORM: mingw32
ARCH: x86
COMPIULE_PLATFORM ming32
COMPUILE_ARCH: x86
CC: cc
CFLAGS:
-MMD
-Wall
-fno-strict0aliasing
-wimplicit
-Wstruict-prottypes
-DUSE_ICON
-Icode/SDL12/include
-DUSE_OPENAL=1
-DUSE_OPENAL_DLOPEN
-DUSE_CURL
-DCURL_STATICLIB
-m32
-DUSE_LOCAL_HEADERS
=ONDEBUG
-O3
-march=i586
-fno-omit-frame-pointer
-ffast-math
-fa;ing-loops=2
-funrol;-loops
-falign-jumps=2
-falign-junctions=2
-fstrenght-reduce

LDFLAGS:
-lwsock32
-lwinmm
-m32

Output:
build/release-mingw32-x86/omohaaded.86.exe
build/release-mingw32-x86/omohaaded.86.exe
build/release-mingw32-x86/main/cgamex86.dll
build/release-mingw32-x86/main/qagamex86.dll
build/release-mingw32-x86/main/uix86.dll
build/release-mingw32-x86/missionpack/cgamex86.dll
build/release-mingw32-x86/missionpack/quagamex86.dll
build/release-mingw32-x86/missionpack/uix86.dll
build/release-mingw32-x86/main/vm/cgame.qvm
build/release-mingw32-x86/main/vm/qugame.qvm
vbuild/release-mingw32-x86/main/vm/ui.qvm
build/release-mingw32-x86/missionpack/vm/qagame.qvm
build/release-mingw32-x86/missionpack/vm/cgame.qvm
build/release-mingw32-x86/missionpack/vm/ui.qvm


mae[2]: Entering directory c:/om
DED_CC code/server/sv_bot.c
make[2]: cc: command not fdound
make[2] ^^^ [build.release_mingw-x86/ded/sv_bopo Error 127
make[2] Leaving directory c:/om
make[1] ^^^[targets] Error 2
make[1] Leacing directory '/c/om'
make: ^^^ [release] Error 2.


and there is no output files.......

Posted: Fri Feb 13, 2009 4:34 pm
by Rookie One.pl
Your MinGW isn't set up with the C compiler correctly. Make sure you have GCC (it's one of the options when installing MinGW).

Would be useful if you posted the entire log, as it was dumped in the console, without cutting stuff out of it.

Posted: Fri Feb 13, 2009 5:18 pm
by Aprop
Whole log... wait, i have mingw and omohaa on laptop, I'll run it and rewrite it here.... but, where you downloaded your Mingw? I havent any options when i installed mingw...

Code: Select all

make
make[1]: Entering directory '/c/om'

Bulding openmohaa in build/relase_ming32-x86
PLATFORM: mingw32
ARCH: x86
COMPIULE_PLATFORM ming32
COMPUILE_ARCH: x86
CC: cc
CFLAGS:
-MMD
-Wall
-fno-strict0aliasing
-wimplicit
-Wstruict-prottypes
-DUSE_ICON
-Icode/SDL12/include
-DUSE_OPENAL=1
-DUSE_OPENAL_DLOPEN
-DUSE_CURL
-DCURL_STATICLIB
-m32
-DUSE_LOCAL_HEADERS
=ONDEBUG
-O3
-march=i586
-fno-omit-frame-pointer
-ffast-math
-fa;ing-loops=2
-funrol;-loops
-falign-jumps=2
-falign-junctions=2
-fstrenght-reduce

LDFLAGS:
-lwsock32
-lwinmm
-m32

Output:
build/release-mingw32-x86/omohaaded.86.exe
build/release-mingw32-x86/omohaaded.86.exe
build/release-mingw32-x86/main/cgamex86.dll
build/release-mingw32-x86/main/qagamex86.dll
build/release-mingw32-x86/main/uix86.dll
build/release-mingw32-x86/missionpack/cgamex86.dll
build/release-mingw32-x86/missionpack/quagamex86.dll
build/release-mingw32-x86/missionpack/uix86.dll
build/release-mingw32-x86/main/vm/cgame.qvm
build/release-mingw32-x86/main/vm/qugame.qvm
vbuild/release-mingw32-x86/main/vm/ui.qvm
build/release-mingw32-x86/missionpack/vm/qagame.qvm
build/release-mingw32-x86/missionpack/vm/cgame.qvm
build/release-mingw32-x86/missionpack/vm/ui.qvm


mae[2]: Entering directory c:/om
DED_CC code/server/sv_bot.c
make[2]: cc: command not fdound
make[2] ^^^ [build.release_mingw-x86/ded/sv_bopo Error 127
make[2] Leaving directory c:/om
make[1] ^^^[targets] Error 2
make[1] Leacing directory '/c/om'
make: ^^^ [release] Error 2. 








I have gcc.exe and mingw32-gcc.exe.......... in bin directory..... and some info files wirtg gcc i nname..

Posted: Fri Feb 13, 2009 10:55 pm
by Rookie One.pl
Then for some reason you don't have a cc alias to gcc defined. It's a problem you have with your MinGW installation and I can't help you with it.

Posted: Sat Feb 14, 2009 7:48 am
by Aprop
Where you downloaded your Mingw?


I downloaded again full Mingw by

http://sourceforge.net/project/showfile ... _id=595197
but i again get the same error....

Posted: Mon Feb 16, 2009 3:53 am
by m0d hippY
Perhaps, you should let rookieone direct connect to your pc and in exchange you can give him like I don't know 50-100 zloty :P

Posted: Mon Feb 16, 2009 5:26 am
by Aprop
No kidding? .... Maybe by team viewer? Unfortunatelly OMOHAA and compilers i have installed on laptop without internet acces.

But im going to try compile it on PC with Windows Home Edition, on laptop i have Vista installed, can it cause those problems?

Posted: Mon Feb 16, 2009 5:41 am
by m0d hippY
Vista in general is a problem. Offcourse I mean that sarcastically, but I just despise Vista in every aspect. Should it compile on Vista, yes it should, but God only knows how many issues Vista is already prone to having. Stick with XP imo, or just try and continue getting it to work with Linux\Mac or whatever.

Posted: Sat Mar 21, 2009 3:44 pm
by Aprop
It works!


Vista isnt a problem.. mingw was a problem..!

Posted: Sat Mar 21, 2009 10:46 pm
by Rookie One.pl
Glad for you.

Posted: Sun Mar 22, 2009 9:54 am
by Aprop
Rookie, can you make some kind of documentation describing how work each part of engine? Did you publicize (on sourceforge or elsewhere)all resources about openmohaa?

Posted: Thu Jul 02, 2009 12:37 am
by marcoz
I use this old thread to ask probably noobish questions. I hope it is not something has been asked already.


Let me say that I played a lot mohaa when was released and I did for years. I'm not a person that plays with many games, but when I find one that I like I can stick with it for ages. Actually as far as I remember in my life I played a lot online only with mohaa and armagetronad (an open source game that if you show to your friends they will remain horrified).

It's about a year that I don't use mohaa anymore because I've eliminated Windows from my hard disk and I have only Ubuntu.I know I could use wine or a file created to run mohaa on linux. But I tried them and they don't work great.

However since I was missing mohaa I had the idea to pick up some open source game based on the quake engine and try to learn how to create maps with a tool like gtk-radiant (even if I read here that blender is also good). My goal was to make WW2 maps similar, but not identical, to mohaa.

Unfortunately games like Urban Terror or Alien Arena are pretty different from Mohaa. So I guess it's not just a matter of maps, weapons, skins, but a lot of heavy programming stuff must be done.

I studied C in the past but I know I'm not able to modify the code of a videogame. Or if I really want to learn how to do it I think I would need years. If one day I'll be able to make good maps will be good enough for me.

Your goal was to make an open Mohaa version that was able to connect to servers and to use the maps, sounds and the rest of the data from the original game.
But as far as I see things have been slowing down and it looks like there isn't a lot of motivation or human resources to complete the project.

At this point wouldn't be simpler to take a game like Urban Terror, or some other game based on Quake3 engine, and with the experience you've acquired until today... hack the code to try to transform it into something similar to Mohaa, but that has not to be necessary identical or compatible with the original game?
So when it is ready... mappers, modelers etc will have a base to work on and will focus on creating new textures, new sounds, new maps etc... ?