Wrecked Games

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're just that awesome.

Author Topic: Autotools OIS Version  (Read 828 times)

dermont

  • Regular
  • *
  • Karma: +0/-0
  • Posts: 23
    • View Profile
Autotools OIS Version
« on: April 05, 2010, 12:56:06 AM »

You've bumped the OIS Version to 1.4.0 in OISPrereqs.h and 1.3.0 in configure.ac.

Also the current autotools build appears applicable to Linux only i.e. you won't be able to build using MingW. I can have a stab at updating them for MingW (unless you feel the Codeblocks projects are adequate) or alternatively creating the CMake files if that's the route you wan't to take.
Logged

tdev

  • Regular
  • *
  • Karma: +0/-0
  • Posts: 20
    • View Profile
Re: Autotools OIS Version
« Reply #1 on: April 05, 2010, 04:00:43 AM »

please be so kind and test the cmake buildsystem i created: http://redmine.rigsofrods.org/issues/206

and tell me whats missing. Thanks!
Logged

pjcast

  • Administrator
  • Veteran
  • *****
  • Karma: +0/-0
  • Posts: 2653
    • View Profile
    • http://www.wreckedgames.com
Re: Autotools OIS Version
« Reply #2 on: April 05, 2010, 07:04:08 AM »

Woops. Meant to bump everything to 1.4.

Not sure what would be involved in updating them to use mingw. Though, there shouldn't be much change involved... If I was trying to cross build something I would use the standard --platform=ARM... or whatever the flag was, and have the autotools pick up the right compiler.

Though, if mingw crossbuild is different, it might be more useful to do it with cmake instead. tdev's cmake patch might be of some use. The only change I would want with the cmake though, would be to have it in its own directory (maybe trunk/ois/cmake) and let it generate project files there. Not sure what folder it is in now (only glanced at it so far).
Logged

dermont

  • Regular
  • *
  • Karma: +0/-0
  • Posts: 23
    • View Profile
Re: Autotools OIS Version
« Reply #3 on: April 05, 2010, 09:01:37 AM »

Not sure what would be involved in updating them to use mingw. Though, there shouldn't be much change involved... If I was trying to cross build something I would use the standard --platform=ARM... or whatever the flag was, and have the autotools pick up the right compiler.

There shouldn't be much changes but it's a bit more involved than ./configure --host=i586-mingw32msvc --build=i386-linux etc. You would have to update the Makefile files to build against the Windows source,, use the dx* headers/libs and create rules for windres to compile and link against the resource files for the exes. I'll post updates later as a matter of interest.

Logged