File: al_build_shader.3

package info (click to toggle)
allegro5 2%3A5.2.6.0-3%2Bdeb11u1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 24,212 kB
  • sloc: ansic: 125,319; cpp: 15,781; objc: 4,579; python: 2,802; java: 2,254; javascript: 1,204; sh: 1,002; makefile: 51; perl: 37; xml: 25; pascal: 24
file content (38 lines) | stat: -rw-r--r-- 912 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
.\" Automatically generated by Pandoc 1.19.2.4
.\"
.TH "al_build_shader" "3" "" "Allegro reference manual" ""
.hy
.SH NAME
.PP
al_build_shader \- Allegro 5 API
.SH SYNOPSIS
.IP
.nf
\f[C]
#include\ <allegro5/allegro.h>

bool\ al_build_shader(ALLEGRO_SHADER\ *shader)
\f[]
.fi
.SH DESCRIPTION
.PP
This is required before the shader can be used with al_use_shader(3).
It should be called after successfully attaching the pixel and/or vertex
shaders with al_attach_shader_source(3) or
al_attach_shader_source_file(3).
.PP
Returns true on success and false on error, in which case the error log
is updated.
The error log can be retrieved with al_get_shader_log(3).
.RS
.PP
\f[I]Note:\f[] 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.
.RE
.SH SINCE
.PP
5.1.6
.SH SEE ALSO
.PP
al_use_shader(3), al_get_shader_log(3)