Maratis forum - Compiling with VC 2005

Re: Compiling with VC 2005

2013-10-01T18:31:33Z

Oooook it works. Thanks.

Re: Compiling with VC 2005

2013-10-01T18:23:46Z

Right, due to my previous adventures with VC 2005 I ended up in tags to see if at least the old version would compile lol.
It's slow but looks like it's compiling now.

Re: Compiling with VC 2005

2013-10-01T18:15:54Z

you are trying to compile a tagged old version of maratis "\tags\Maratis-3.01",

open a command line and go to trunk/dev/
type : "python scons.py"

after the build, the final product can be found in the "prod/" directory

if you don't want to type it each time in a command line,
create a bat in trunk/dev with :

python scons.py
pause

Re: Compiling with VC 2005

2013-10-01T18:04:58Z

So I tried VC 2008 with scons & python 2.7 but I got

SyntaxError: Non-ASCII character '\xc3' in file [...]\maratis\tags\Maratis-3.01\var\scons\thirdparty\bullet.py on line 3, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details

Found solution here: http://stackoverflow.com/questions/1058 … on-returns

After that, though, I got

Build in release mode
Using 3rdparty libraries in folder: [...]\maratis\3rdparty
NameError: global name 'os' is not defined:
  File "[...]\maratis\tags\Maratis-3.01\SConstruct", line 71:
    exports='env' )
  File "[...]\maratis\tags\Maratis-3.01\scons-local-2.0.1\SCons\Script\SConscript.py", line 614:
    return method(*args, **kw)
  File "[...]\maratis\tags\Maratis-3.01\scons-local-2.0.1\SCons\Script\SConscript.py", line 551:
    return _SConscript(self.fs, *files, **subst_kw)
  File "[...]\maratis\tags\Maratis-3.01\scons-local-2.0.1\SCons\Script\SConscript.py", line 260:
    exec _file_ in call_stack[-1].globals
  File "[...]\maratis\tags\Maratis-3.01\Maratis\SConscript", line 19:
    exports='env' )
  File "[...]\maratis\tags\Maratis-3.01\scons-local-2.0.1\SCons\Script\SConscript.py", line 614:
    return method(*args, **kw)
  File "[...]\maratis\tags\Maratis-3.01\scons-local-2.0.1\SCons\Script\SConscript.py", line 551:
    return _SConscript(self.fs, *files, **subst_kw)
  File "[...]\maratis\tags\Maratis-3.01\scons-local-2.0.1\SCons\Script\SConscript.py", line 260:
    exec _file_ in call_stack[-1].globals
  File "[...]\maratis\tags\Maratis-3.01\Maratis\Editor\SConscript", line 34:
    thirdparty.openal.addOpenALToEnv(env_local)
  File "[...]\maratis\tags\Maratis-3.01\var\scons\thirdparty\openal.py", line 51:
    vincludepath.append(os.path.join(env['thirdpartydir'],pth))

Re: Compiling with VC 2005

2013-10-01T14:51:21Z

Oh, ok, didn't think about that. I had errors compiling the Player and the Editor so I though I could just use the "old" ones.
So now I have to either try to solve those errors or try scons with VC 2010/08.

Re: Compiling with VC 2005

2013-10-01T13:52:59Z

scons is the only up to date system.

the vc project might need some updating (if new file code was added),
but one thing is, if you compile MCore and MEngine,
you also have to recompile the editor with MCore.dll and MEngine.dll,
because the entry points are not necessary the same.

Compiling with VC 2005

2013-10-01T08:54:21Z

So I was trying to compile with VC 2005 since you seem to use that one.
After some fails, I've succeded compiling MCore and MEngine from the /tags release but their size is different than the original and if I try to launch the Editor/Player (after copying the DLLs) it says "impossible to find the entry point [name of the entry point with crap characters] of the procedure on MEngine.dll" (approximate translation from my OS language).
Any idea?
I thought this was better than installing with scons and new VC versions but maybe currently only scons works?