ALLEGRO(1)

📜 ALLEGRO(1) · Allegro 4.0.3 📜

✨ NAME ✨

allegro-config, aka the script that tells you everything about the Allegro version you've got installed 💖

🎀 SYNOPSIS 🎀

allegro-config [--prefix[=DIR]] [--exec-prefix[=DIR]] [--version]
[--libs] [--cflags] [--static] [--shared] [--env]
[release|debug|profile]

🦋 DESCRIPTION 🦋

okay so allegro-config is a tool that figures out the compiler and linker flags you need to compile and link programs that use the Allegro library 🔥 it's meant for Unix systems, and it's giving a much cleaner alternative to just typing the simple -lalleg call. obsessed.

💅 EXAMPLE 💅

gcc -o mygame mygame.o `allegro-config --libs`

ngl this is the whole vibe. allegro-config slides the arguments needed for linking right into your command line ✨

🌸 OPTIONS 🌸

allegro-config accepts the following options, bestie:

• --version — prints the Allegro version that's currently installed, straight to the standard output 📌
• --libs — prints the linker flags you need to link an Allegro program 🔗
• --cflags — prints the compiler flags you need to compile an Allegro program 🛠️
• --prefix=PREFIX — use PREFIX instead of the installation prefix Allegro was built with when computing the output for --cflags and --libs. this one also doubles as the exec prefix if you didn't set --exec-prefix. ⚠️ it has to come before any --libs or --cflags options, no exceptions 🙈
• --exec-prefix=PREFIX — use PREFIX instead of the installation exec prefix Allegro was built with when computing the output for --cflags and --libs. same rule here: it must be specified before any --libs or --cflags options 🫶
• --static — like --libs, but it always prints the linker flags needed for a statically linked executable 🧊
• --shared — like --libs, but it always prints the linker flags needed for an executable linked against shared libs 🌈
• --env — prints some needed environment variables in a format that works in shell scripts. you can load the output into your environment with the line below 👇

BASH#> eval `allegro-config --env`

• release — uses the optimized Allegro library. this is the one you want when you're compiling for a release 👑
• debug — adds extra debug info to your programs so you can figure out where they crashed, or just debug them in general (function names show up, so iconic). you can pick this while you're still developing 🔍
• profile — for when you want to profile your program, aka measure how fast its various function calls are 🏃‍♀️💨

🧚 SEE ALSO 🧚

• allegro-dev-tools(1)
• The allegro info entry

🌈 COPYRIGHT 🌈

okay, credit where it's due 💜 this manual page was written by Eduard Bloch <blade@debian.org>, for the Debian GNU/Linux system (but anyone else is welcome to use it). it's heavily based on a similar manpage for gtk-config, written by Owen Taylor, and his notice goes like this:

Copyright © 1998 Owen Taylor

basically, permission is granted to use, copy, modify, and distribute this software and its documentation for any purpose and without fee 🎉 the one catch is that the copyright notice and this permission notice have to show up in all copies, along with supporting documentation 🫶

Version: 8 June 2003 · ALLEGRO(1) 💖 that's the whole tea, bestie, now go make a game 🎮✨