Compiling under Mac OS X

[alihelmy]

hey mates,

I was wondering if someone has tried it before (or if it is at all possible) to compile glest under Mac OS X, as i really wanna try having it run on my macbook...

[hailstone]

I found this on the forum. http://www.glest.org/glest_board/postin ... ply&t=1717

[alihelmy]

I found this on the forum. http://www.glest.org/glest_board/postin ... ply&t=1717

I'm sorry, you've put down the wrong link... what were you pointing at?

[hailstone]

Sorry. I must have a copied the url from the wrong window. Here is the correct one http://www.glest.org/glest_board/viewtopic.php?t=689

[alihelmy]

Well, the thread is taking about PPC macs, but my macbook is running an intel Core 2 Duo processor...

So, how about there, any chances of getting it to compile on an intel mac?

[hailstone]

From Wkipedia on Mac OS X:

Because Mac OS X is, unlike its predecessors, based on UNIX, most software packages written for BSD or Linux can be recompiled to run on it.

Changes might be needed in the Jamconfig.

[alihelmy]

From Wkipedia on Mac OS X:

Because Mac OS X is, unlike its predecessors, based on UNIX, most software packages written for BSD or Linux can be recompiled to run on it.

I know, that is why i did not freak away when i realised there is no mac version... i have had similar games that only worked on windows/linux and ive compiled them successfully on my macbook

Changes might be needed in the Jamconfig.

Well, i guess then i will download the source code and then i will try and compile it, and keep you updated, so we can walk through what changes are needed

[alihelmy]

Hey mates,

I found this thread that describes how to build the code... I read it and understood the arrangement of the code, however, all the required libraries are listed for compiling on a Win platform

So any ideas about what is needed for building on Mac OS X (or FreeBSD?)

PS: that thread is locked, and it is not complete, any plans to follow on with it?

[hailstone]

Wouldn't the libraries be the same? and i think you would need to edit the sources to use other libraries unless it already lets you do that.

[alihelmy]

Libraries needed to compile the Glest code:

Windows OpenGL: opengl32.lib, glu32.lib

DirectX 9 SDK: dsound.lib, dxguid.lib

Xerces C++: An XML parser, can be downloaded from: http://xml.apache.org/.

Ogg Vorbis Win32 SDK: Ogg audio files decoder, can be downloaded from http://www.vorbis.com/

SGI OpenGL SDK: SDK for accessing OpenGL +1.1 and extension functionality: http://oss.sgi.com/projects/ogl-sample/sdk.html. (Files used: gl.h, glu.h, glprocs.h, glprocs.c)

So, you see, the problem is that the libs include things that are Win32 specific, like the DirectX9 SDK for sound...

so, what will i do to get around it?[/quote]

[Fusselbaer]

Hello alihelmy,

perhaps you can look in the FreeBSD Makefile vor Glest:
http://www.freebsd.org/cgi/cvsweb.cgi/~ ... xt%2Fplain

In this Plain Text FreeBSD Ports Makefile for Glest
you can see LIB_DEPENDS= the Libs, you need.

And you can see wich tool for Build (jam):
http://www.perforce.com/jam/jam.html

A good overview, over the used FreeBSD Ports and
URLs for the Depends is:
http://www.freshports.org/

A second Port for Glest is the glest-data Port:
http://www.freebsd.org/cgi/cvsweb.cgi/~ ... xt%2Fplain

Glest is on FreeBSD split in 2 Parts:
the glest port for bullding (compile) the exec binarys
and
the glest-data Port for the xml Files and the "Pics",
like  g3d, tga, bpm
and the Sound, like ogg and wave.


Hope, that can help you a little bit.
Im only a FreeBSD x86 User,
have no Mac Box.  :cry:    


Greetings, Fusselbaer

[hailstone]

Glest seems to use the Abstract Design Pattern which provides a way to encapsulate a group of individual factories that have a common theme, such as using different sound libraries for different OS types. (In the shared_lib/sound folder there is a folder for direct sound 8 and openAL. On a Linux system the direct sound files are ignored and the openAL files are used.)

If the compiler complains about not finding the DirectX libs remove the encapsulated dx files from the project include files.

Mac uses OpenGL for graphics and can use http://www.un4seen.com/ (is free for non-commercial use) for sound. I think xerces can be compiled under Mac.

[bloedneus]

I tried using the linux guide in the macosx terminal. I think i installed all the needed libraries. This is what i do:

MacBookPro:~/glest/trunk/mk/linux jjb$ ls
Jamfile         autogen.sh      glest.ini       mk
Jamrules        configure.ac    makerelease.sh
MacBookPro:~/glest/trunk/mk/linux jjb$ ./configure
-bash: ./configure: No such file or directory

What did i do wrong?

[Fusselbaer]

Have you the Rights? (Unix Rights)

Or you need something to run ./configure

Here is a Place for Apple User for getting Devel Tools:
http://pdb.finkproject.org/pdb/section.php/devel
autoconf, automake...  

Here is the Fink F.A.Q.:
http://www.finkproject.org/faq/index.php?phpLang=en


Greetings, Fusselbär

[bloedneus]

i already installed the libraries with macports because i couldnt find all of them with fink.
Im a noob at this and i just figured out that you have to do aclocal and autoconf before ./configure. When i do aclocal and autoconf before ./configure i get a bit further.

MacBookPro:~/glest/mk/linux jjb$ ls
Jamfile         Jamrules        autogen.sh      configure.ac    glest.ini       makerelease.sh  mk
MacBookPro:~/glest/mk/linux jjb$ aclocal
MacBookPro:~/glest/mk/linux jjb$ autoconf
configure.ac:58: error: possibly undefined macro: AC_MSG_ERROR
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.ac:140: error: possibly undefined macro: AC_INIT_JAM


What do those two errors mean?

[Auria]

i already installed the libraries with macports because i couldnt find all of them with fink.
Im a noob at this and i just figured out that you have to do aclocal and autoconf before ./configure. When i do aclocal and autoconf before ./configure i get a bit further.

MacBookPro:~/glest/mk/linux jjb$ ls
Jamfile         Jamrules        autogen.sh      configure.ac    glest.ini       makerelease.sh  mk
MacBookPro:~/glest/mk/linux jjb$ aclocal
MacBookPro:~/glest/mk/linux jjb$ autoconf
configure.ac:58: error: possibly undefined macro: AC_MSG_ERROR
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.ac:140: error: possibly undefined macro: AC_INIT_JAM

What do those two errors mean?

i suggest following install instructions

usually, when you get stuff from SVN, you need to run autogen first, NOT autoconf and aclocal.

./autogen

If you got a source tarball usually you can run configure right ahead.