| Re: [AD] 5.0.0 final release plan |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Sun, Jan 2, 2011 at 1:55 AM, Evert Glebbeek <eglebbk@xxxxxxxxxx> wrote:
> Try the attached patch.
That looks OK for ALLEGRO_SYSTEM_DATA_PATH; a5teroids does work now
with this patch *and* with al_get_standard_path(ALLEGRO_PROGRAM_PATH)
replaced by al_get_standard_path(ALLEGRO_SYSTEM_DATA_PATH) in
Game.cpp. However I don't know if this would break every other
platform?
> Check whether ALLEGRO_PROGRAM_PATH and ALLEGRO_EXENAME_PATH make sense to you. They come out the same here, except one is a directory and the other is not. Not sure what the correct behaviour is for a bundle, although I suspect that everything is fine if ALLEGRO_PROGRAM_PATH just drops the last path component (which is the name of the bundle).
I think you're right about dropping the last component. I can't really
think of a use for those two, but does ALLEGRO_EXENAME_PATH have to
point to the real executable or not?
Pete