GPipe: A functional graphics API for programmable GPUs
|Versions||1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7, 1.2.0, 1.2.1, 1.3, 1.3.1, 1.3.2, 1.4, 1.4.1, 2.0, 2.0.1, 2.0.2, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.1.6, 2.1.7, 2.1.8, 2.2, 2.2.1, 2.2.2, 2.2.3 (info)|
|Dependencies||base (>=3 && <5), Boolean (==0.0.1), containers (>=0.2 && <0.4), GLUT (==18.104.22.168), list‑tries (==0.1.*), mtl, OpenGL (==22.214.171.124), Vec (==0.9.6), Vec‑Boolean (==1.0.2) [details]|
|Uploaded||by TobiasBexelius at Fri Mar 12 18:05:13 UTC 2010|
|Distributions||LTSHaskell:2.2.3, NixOS:2.2.3, openSUSE:2.2.3|
|Downloads||12880 total (97 in the last 30 days)|
|Rating||(no votes yet) [estimated by rule of succession]|
|Status||Docs uploaded by user
Build status unknown [no reports yet]
Hackage Matrix CI
GPipe models the entire graphics pipeline in a purely functional, immutable and typesafe way. It is built on top of the programmable pipeline (i.e. non-fixed function) of OpenGL 2.1 and uses features such as vertex buffer objects (VBO's), texture objects and GLSL shader code synthetisation to create fast graphics programs. Buffers, textures and shaders are cached internally to ensure fast framerate, and GPipe is also capable of managing multiple windows and contexts. By creating your own instances of GPipes classes, it's possible to use additional datatypes on the GPU.
You'll need full OpenGL 2.1 support, including GLSL 1.20 to use GPipe. Thanks to OpenGLRaw, you may still build GPipe programs on machines lacking this support.
Note on installation: If you have cabal installed list-tries with flag containers03 (you should) then use the same flag when installing GPipe. This flag is false by default since it's false for list-tries as well, and I want Hackage to be able to build it.
Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info
For package maintainers and hackage trustees