Exult Forum

Okay Im trying to get a snapshot for OS X folks going again..
Been outta the loop since June or so (when all the big changes were made and stuff started breaking) but here we go again..

http://www.monotrematamusic.com/exult/E ... 1.4cvs.dmg

Some notes..

This is PPC ONLY!!!! This was a command line build so I couldnt compile it as a UB yet.. I found some problems with my SDL config that may have caused it to break when moving from one system to another last time we tried this..
To make it simple, Ive gotten rid of SDL via Fink and am using the Mac OS X versions which you will need to download and install from here:

http://www.libsdl.org/download-1.2.php

The file goes in /Library/Frameworks

Remember to mount the .dmg and copy everything inside to your Ultima 7 folder (mine lives in /Applications/Ultima 7). The data folder has to be in the directory with the Exult.app or the app wont work. No matter what Ive tried to get it to use the ones inside the Exult app it wont work with the internal ones..

So if a good old PPC user can test this for me and let me know if it works or not, Ill go ahead and put it back into XCode and move towards a UB version again. Im hoping this SDL thing was my problem last time.. Ill check back in a couple of days and see if theres any feedback.. If it works perhaps I can finally help out and make some current OS X snapshots here regularly (since 1.2 is a 'little' outdated)..

Oh BTW - This was cvs source from about 12:59pm today, 10/14/08.

Ok so my link to the dmg didnt work for some reason (space in the name maybe??) so just copy/paste that entire thing into your browser to grab it..

Any trouble with the file just let me know and Ill fix it..

I tried to fix the link, but (strangely) even url-encoding the space didn't do it. In any case, I left it with the url-encoded space so that the link can be recognized correctly by auto-linkification browser extensions/plug-ins.

The build won't run for me. The error is

10/15/08 12:12:06 PM [0x0-0x275275].Exult[40557] dyld: Library not loaded: /usr/local/lib/libSDL_mixer-1.2.0.dylib
10/15/08 12:12:06 PM [0x0-0x275275].Exult[40557] Referenced from: /Users/MeddlingMonk/Downloads/Exult.app/Contents/MacOS/exult
10/15/08 12:12:06 PM [0x0-0x275275].Exult[40557] Reason: image not found
10/15/08 12:12:07 PM com.apple.launchd[183] ([0x0-0x275275].Exult[40557]) Exited abnormally: Trace/BPT trap

I get the same error trying it from terminal.

Hrm.. So I DO still have SDL installed manually!!! Sorry forgot about that..

Err.. Lemme remove that one and see if it will compile again using the SDL.Framework instead..

Well it dont work with the Frameworks installed from the SDL site. So far it only works if I have it compiled and installed via command line.
No clue how to get it to use the files in /Library/Frameworks instead of the one installed in /usr/local/lib..

Checking out the contents of the SDL.Framework folder there arent even any libraries just .h files. None of the dylib's that Exult needs. Perhaps they get compiled on the fly or something when youre developing a Mac app in XCode.

./configure ends with this message:
./configure: line 24357: syntax error near unexpected token `$SDL_VERSION,'
./configure: line 24357: `AM_PATH_SDL($SDL_VERSION,'

And this always comes up beforehand when I run ./autogen.sh:
configure.ac:306: warning: macro `AM_PATH_SDL' not found in library
configure.ac:22: installing `./missing'
configure.ac:22: installing `./install-sh'
configure.ac:307: error: possibly undefined macro: AM_PATH_SDL


But if I use the source and make install it like normal, it works fine.

Guess the Mac will just have to do it like a Linux system and install SDL by way of good old source code compiling. Unless someone can show me how to get the ./autogen and ./configure to use the other one but from what Ive looked up sounds like it only works under XCode..

K here goes round 1200089234089

Any thoughts on when a version for Intel Leopard machines can be out?

Well for kicks Im building my old xcode project right now but even if it makes it all the way to the exult.app target, until someone installs SDL in their /usr/local/bin directories, we dont even know if it will move from machine to machine yet let alone actually compile as a universal binary.

as it stands now, if the SDL installation enabled this app to move from Mac to Mac, compiling Exult via command line still requires a PPC user and an Intel user to each make their own app to distribute.

To build universal binaries from the command line, pass these flags to gcc/g++:

-isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc

I think the '-arch' ones need to be given to ld too.

To link frameworks instead of unfriendly (*cough* ugly, horrible, evil *cough*) fixed-location libraries you need the following in CFLAGS:

-F/Library/Frameworks
-I/Library/Frameworks/SDL.framework/Headers
-I/Library/Frameworks/SDL_mixer.framework/Headers (does exult use mixer?)

and to the linker:

-L/Library/Frameworks
-framework Cocoa
-framework SDL
-framework SDL_mixer

(listed on separate lines for readability)

P.S. You can also copy the SDL framework (and any other frameworks) into the exult application bundle once you're finished. That way users don't have to download and install them separately, which they shouldn't have to do.

Just 'cp -R' each framework into Exult.app/Contents/Frameworks/

Ok back on now after months of inactivity!
Mac died so Im back on Tiger now, just got everything back up and now I gotta build Exult again!

Picking up where I left off in October, how and where do I add those CFLAGS variables and how/where do I put that linker info as well?

If someone could let me know Ill be back on track!