al_build_shader(3)

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

πŸ’– NAME πŸ’–

okay so this page is al_build_shader(3), and it lives in the Library Functions Manual β€” Allegro 5 API bestie central ✨

  • al_build_shader β€” Allegro 5 API

✨ SYNOPSIS ✨

#include <allegro5/allegro.h>

bool al_build_shader(ALLEGRO_SHADER *shader)

πŸ› οΈ DESCRIPTION πŸ› οΈ

bestie, this function is the required glow-up step before your shader can be used with al_use_shader(3) πŸ’… It should be called after you’ve successfully attached the pixel and/or vertex shaders with al_attach_shader_source(3) or al_attach_shader_source_file(3). No skipping the line, okay?

It returns true on success and false on error β€” and when it errors, the error log is updated 😭 You can retrieve that error log with al_get_shader_log(3).

Note: If you are using the ALLEGRO_PROGRAMMABLE_PIPELINE flag, then you must specify both a pixel and a vertex shader sources for anything to be rendered. That’s not a suggestion, bestie β€” both sources or nothing renders πŸ’€

⭐ SINCE ⭐

5.1.6


πŸ‘€ SEE ALSO πŸ‘€


🌸 ok bye bestie β€” signing off from the Allegro reference manual, al_build_shader(3) edition, version vibes 5.1.6, with no date drama in the footer and still iconic πŸ’–βœ¨

πŸ“¦ 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