| Re: [AD] [ alleg-Bugs-1223257 ] Mac OSX allegro will not read config files |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Saturday, June 18, 2005, at 06:52 pm, SourceForge.net wrote:
I have noticed that the Mac OSX version of the 4.2 beta
allegro won't read any data from a config file. At
first I thought that it was something that I was doing
wrong, but the example program exconfig has the same
problem. The set_config_file() doesn't crash or
anything. The get functions just return 0 or NULL.
Writing to the config files works just fine. I have
tested this using Mac OS 10.3.9 and 10.4.1 with xcode
1.2 (not xcode 2.0).
I commented on this on the bug tracker. I'm not sure if it will get
posted here, so I'll repeat it. I should also point out that I don't
think it's a Mac-specific issue.
Date: 2005-06-18 18:55
Sender: proto_potty
Logged In: YES
user_id=1299108
I just found that it the example program exconfig will read
the config file if it is run from the terminal in the same
directory as the config file. But if you run it from any
other directory (like ./examples/exconfig from the allegro
root directory) or from finder, it will not load.
Date: 2005-06-19 19:50
Sender: peterhull90
Logged In: YES
user_id=295085
I don't think this is a bug. From my interpretation of the
documentation, Allegro will search various paths, including the
executable directory, _only_ for the allegro.cfg file. If you specify
your own config file, as exconfig does, it will look in the place
that you specified, so if you gave it a path-less filename, it will
look in the current directory only.
I think an argument could be made that this behaviour is rather
useless, and it should search the executable directory, that is not
what the docs say.
Pete