Developed by:

AlloSphere Research Group

University of California, Santa Barbara

The API documentation can be found at: https://allosphere-research-group.github.io/allolib-doc/

Allolib only depends on Cmake version 3.8 (as the build tool), OpenGL and glew.

On a bash shell on Windows, Linx and OS X do:

git clone https://github.com/AlloSphere-Research-Group/allolib
cd allolib
git submodule init
git submodule update
./run.sh examples/graphics/2d.cpp

The simplest way to compile and run a single file in allolib is by using the run.sh script:

./run.sh path/to/file.cpp

This will build allolib, and create an executable for the file.cpp called 'file' inside the '''path/to/bin''' directory. It will then run the application.

You can add a file called '''flags.cmake''' in the '''path/to/''' directory which will be added to the build scripts. Here you can add dependencies, include directories, linking and anything else that cmake could be used for. See the example in '''examples/user_flags'''.

For more complex projects follow the example provided in the empty/project directory. This requires writing a CMakeLists.txt to specify sources, dependencies and linkage.

#TODO

• fullscreen with specific monitor

• freeimage (optional)
• freetype (optional)
• assimp (optional)

If these are avaialble, the classes that use them will be built. A simple alternative is to use the image/font/asset loading provided in the modeules directory. These classes depend on header only libraries that are included in these sources.