al_set_exe_name(3alleg5)

πŸ“¦
version 5.2.11.3 Β· 4 versions
, in debian trixie, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– 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 πŸŽ€


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