.\" Automatically generated by Pandoc 2.17.1.1 .\" .\" Define V font for inline verbatim, using C font in formats .\" that render this, and otherwise B font. .ie "\f[CB]x\f[]"x" \{\ . ftr V B . ftr VI BI . ftr VB B . ftr VBI BI .\} .el \{\ . ftr V CR . ftr VI CI . ftr VB CB . ftr VBI CBI .\} .TH "al_get_system_config" "3alleg5" "" "Allegro reference manual" "" .hy .SH NAME .PP al_get_system_config - Allegro 5 API .SH SYNOPSIS .IP .nf \f[C] #include ALLEGRO_CONFIG *al_get_system_config(void) \f[R] .fi .SH DESCRIPTION .PP Returns the system configuration structure. The returned configuration should not be destroyed with al_destroy_config(3alleg5). This is mainly used for configuring Allegro and its addons. You may populate this configuration before Allegro is installed to control things like the logging levels and other features. .PP Allegro will try to populate this configuration by loading a configuration file from a few different locations, in this order: .IP \[bu] 2 \f[I]Unix only:\f[R] /etc/allegro5rc .IP \[bu] 2 \f[I]Unix only:\f[R] $HOME/allegro5rc .IP \[bu] 2 \f[I]Unix only:\f[R] $HOME/.allegro5rc .IP \[bu] 2 allegro5.cfg next to the executable .PP If multiple copies are found, then they are merged using al_merge_config_into(3alleg5). .PP The contents of this file are documented inside a prototypical \f[V]allegro5.cfg\f[R] that you can find in the root directory of the source distributions of Allegro. They are also reproduced below. .PP Note that Allegro will not look into that file unless you make a copy of it and place it next to your executable! .IP .nf \f[C] __ALLEGRO_5_CFG \f[R] .fi