al_set_exe_name(3alleg5)
π NAME π
al_set_exe_name β the Allegro 5 API girlie who lets you tell Allegro which executable is actually running, bestie π
β¨ SYNOPSIS β¨
#include <allegro5/allegro.h>
void al_set_exe_name(char const *path)
πΈ DESCRIPTION πΈ
Okay so basically this function overrides the executable name that al_get_standard_path(3alleg5) uses β specifically for ALLEGRO_EXENAME_PATH and ALLEGRO_RESOURCES_PATH. That's it, that's the whole vibe. π¦
One situation where changing this is actually useful: if you're using the Python wrapper. See, Allegro would otherwise just assume the system's Python executable is the current executable β which is giving β¨wrong main characterβ¨. But ngl, you can set it to the .py file being executed instead, and suddenly everything makes sense. ππ
β SINCE β
5.0.6, 5.1.0 β she's been here a minute, no cap π
π SEE ALSO π
al_get_standard_path(3alleg5)β the bestie she's literally built for π«Ά
And that's a wrap on the Allegro reference manual entry for al_set_exe_name(3alleg5)**, part of the Allegro 5 API, dated <cyan>al_set_exe_name(3alleg5)`-o'clock π slay, go set that exe name, periodt ππ§
π¦ where this page comes from
- debian trixie: allegro5-doc 2:5.2.10.1+dfsg-1 Β· Zlib
- ubuntu questing: allegro5-doc 2:5.2.10.1+dfsg-1build1
- ubuntu resolute: allegro5-doc 2:5.2.11.3+dfsg-1 Β· Zlib
- ubuntu stonking: allegro5-doc 2:5.2.11.3+dfsg-1 Β· Zlib
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms