Build problem for Mac OS X

[Clock Nova]

No luck getting it to locate the BG data files by setting the absolute pathway in the config file. How come there is no already a config file in the folder?

[Clock Nova]

putting the config file in my home directory has no effect. Could you post a copy of your config file for comparison?

[Marc]

try following my instructions from 03-22-03 02:54

both versions 1.1.x and 1.0.0 use the config file in your home dir. not in the current folder from that you start exult.

Assuming your username is 'nova', the exult uses the following config config file: /Users/nova/.exult.cfg

my config file can be downloaded at:

http://www.stud.uni-hannover.de/~kleineb/.exult.cfg

[Clock Nova]

Again, no effect, even when in my home directory.

Your config file is not there.

[Clock Nova]

I know that I must be doing something wrong here, but maybe you can help me. Let's assume that I have downloaded and uncompressed the 1.1 package. I have placed the resulting folder in my Applications folder, and into that I have placed my "blackgate" and "serpentisle" folders, within each of which are the "static" and "gamedat" folders.

In addition, I have placed the "exult.cfg" file in my home directory, though it is not currently properly set up to run the game.

Now, what exactly do I need in my config file to correctly let Exult know where everything is? Also, is there somewhere that I need to set a path so that Exult knows where my config file is?

Maybe you can help me out by just posting a clip from your config file.

[wjp]

> In addition, I have placed the "exult.cfg" file in my home directory

The file is supposed to be named ".exult.cfg". Note the leading dot.

[Clock Nova]

OSX does not allow filenames to begin with a dot. There's no way I can do it. Why is this now necessary?

What do you suggest?

[wjp]

I have no idea. Just repeating what Marc said

[fingolfin]

You most definitly *can* create files starting with a dot in Mac OS X. Those files are then (as on all Unix systems) invisible.

And normally, "exult.cfg" (w/o a leading dot) works fine over here (with my own build; I didn't try the build used here).

[wjp]

Here's the logic for which config file we read:

if XWIN is defined, and BEOS isn't defined, use $HOME/.exult.cfg
if XWIN and BEOS are defined, use $HOME/config/settings/exult.cfg
(If the HOME environment variable is set. Otherwise it falls back to exult.cfg)

Otherwise, use exult.cfg


(By "if XYZ is defined", I mean if it was defined during the build process)

[Marc]

I find it unaesthetic that a exult.cfg (w/o leading dot) appears when I start exult. So I modified the sources, that OSX is treaded linke Linux, so that exult will use the ~/.exult.cfg (w/ a leading dot in the home dir).

As Fingolfin said these files are invisible, but they can be opened with normal editors....

[wjp]

Ah, so you modified that logic

Feel free to ignore my post, then

[Marc]

....in a shell a the 'dotfiles' can be displayed with 'ls -a', or 'ls -la'

[wjp]

Btw, I don't want to sound too pedantic, but if you distribute Exult binaries from modified sources, you have to make the sources available too because of the GPL. (Or for example a patch against the version of Exult you used.)

If the config file thing is the only thing you changed it should be a very tiny patch

[Clock Nova]

Okay, this may all be beyond me. I think I am just going to have to wait for Apple to address the bug that is preventing the official binary release.

Thanks for the effort, anyway.

[Marc]

Okay that GPL thing....

I made a diff, takes less space than the sources...What about regenerated configure script and Makefiles with the *auto tools? I have modified my libstdc++ and compiler what does GPL say to this?

http://www.stud.uni-hannover.de/~kleine ... 0-patch.gz
http://www.stud.uni-hannover.de/~kleine ... s-patch.gz

BTW: a patch against the 1.0 version (including the new makefiles...) _was_ available on my PC (see message from 02-02-03 11:52). It was, cause I installed my PC new, but didn't setup the webserver again....

[matt]

it works good for me....but I'm not sure what I did to make it work...I just threw all the files into one folder.

[Clock Nova]

Curse you.

Could you post the section of your config file that lists the pathways for the various files and folders?

[Clock Nova]

OKAY! I finally got the 1.1 build working. I had no idea that the config file was going to be invisible and that I would have to edit it via the command line (I still don't know how to make invisible items visible in OSX).

Why is it that the config file is invisible and in the home directory in this build? Will it always be this way?

By the way, I'm trying to get SDL installed on my machine so I can get the Ultima IV remake running, but I have no idea what I'm doing. Does anyone know the location of a good SDL on OSX tutorial?

[Marc]

congratulations!

to summarize this thread:

I have changed the sources to use the '.exult.cfg' (w/ leading dot) in the home directory, cause I don't like a config file floating around. A file with a leading dot is always 'invisible' on OS X, as on all Unix-ish systems. Fingolfin thought yesterday of putting the config file in an official exult in OS X's standard path for config files (~/Library/Preferences/Exult Preferences)

[Clock Nova]

I'm all for putting it in a Preferences folder.

[Danjuro]

A little thread necromancy here

Just to say Apple finally released an update for the December 2002 tools, you can get it from there

http://developer.apple.com/tools/

Hope it will fix the previous issue.

Best regards.

[wjp]

Yes, they fixed the issue

[Clock Nova]

Does this mean we will soon see an "Official" OSX release of Exult 1.1 on the downloads page? Can it be?

[Dominus]

The chances are you will se an official 1.0 and when we release a version of the 1.1.x tree of that one as well...

[Clock Nova]

Cool. Since I'm already using a painstakingly compiled version from the 1.1.x tree (thanks to this thread) I'll just wait until that one.

Thanks guys!

[kuran]

Great news, can't wait!