Re: [AD] al_set_win_dll_path

[Matthew Leverton <meffer@xxxxxxxxxx>]

On Mon, Jul 25, 2011 at 5:12 PM, Elias Pschernig
<elias.pschernig@xxxxxxxxxx> wrote:
> Yes, and PATH worked in the past. But this patch changes it to hardcode
> the path to next to the .exe:
>
Hmm, maybe a different, more general solution is:

al_set_exe_name("c:/foo/game.py")

Because don't you have a problem with
al_get_standard_path(ALLEGRO_RESOURCES_PATH) returning the python
directory?

The above function would affect the library loading location in
Windows. It would also adjust the RESOURCES_PATH to be "c:/foo" in
this case. It would affect what Linux and OS X (non-bundles) report
for RESOURCES_PATH as well.

--
Matthew Leverton