al_set_exe_name(3)

πŸ“¦
version 5.2.11.3 Β· 3 versions
, in arch rolling

πŸ’– al_set_exe_name(3) πŸ’–

okay bestie, welcome to the Library Functions Manual β€” this one is short, iconic, and lowkey a little niche, but we’re gonna slay it ✨


🌸 NAME 🌸

al_set_exe_name β€” Allegro 5 API πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

#include <allegro5/allegro.h>

void al_set_exe_name(char const *path)

πŸ’… DESCRIPTION πŸ’…

So this function overrides the executable name that al_get_standard_path(3) uses for these two paths, periodt:

  • ALLEGRO_EXENAME_PATH
  • ALLEGRO_RESOURCES_PATH

One situation where changing this is genuinely useful is if you use the Python wrapper 🐍. Without this override, Allegro would by default think that the system’s Python executable is the current executable β€” but you can set it to the .py file being executed instead. Main character energy, fr fr πŸ’–


⭐ SINCE ⭐

5.0.6, 5.1.0 β€” yes bestie, both of those πŸ’«


πŸ”₯ SEE ALSO πŸ”₯


Signing off from the Allegro reference manual, page al_set_exe_name(3) β€” the footer didn’t give me a date, so no invented date, just vibes and accurate facts πŸ’…βœ¨πŸ«Ά

πŸ“¦ where this page comes from
  • arch rolling: allegro 5.2.11.3-2 Β· Zlib AND BSD-3-Clause AND OFL-1.1 AND LicenseRef-Custom
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms