SiegeLord

Going via a temporary buffer works however.

A user had trouble with static linking on Linux, where `libXss` wasn't being found. It's possible that its path was not placed in the output of `pkg-config --static`.

For utility functions, we could have `al_map_pcm(conf, depth, channels...)` and `al_unmap_pcm(void*, conf, depth, *channels)`

Right now it's mostly documented in the `allegro5.cfg` (and a little bit in the `al_register_trace_handler`). We should have a dedicated section for this (also, confirm that `allegro.log` is created in...

Right now we just report whether the component will be built or not, but disregard whether it was wanted or not.

Add some prefabricated sound effects

9

The mixer has `al_set_mixer_postprocess_callback` function. We should provide a bunch of pre-made effects. An API could be: ```c ALLEGRO_DELAY_AUDIO_EFFECT *al_create_delay_audio_effect(delay_secs, channel_conf, channel_depth, frequency); pp_callback_t al_get_audio_effect_callback(ALLEGRO_DELAY_EFFECT *effect); al_destroy_audio_effect(ALLEGRO_DELAY_EFFECT *effect); ``` And...

Consider annotating the public API with visibility annotations

1

Relevant flags/attributes: ``` -fvisibility=hidden __attribute__((visibility("default"))) __attribute__((visibility("protected"))) ```