Skip to content
Library for interactive multimedia application development
C++ CMake
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
doc
examples
external Multiple fixes to implement functionality from master branch Jul 26, 2019
include/al Merge branch 'devel' of https://github.com/AlloSphere-Research-Group/… Dec 27, 2019
src Fixed outstanding issue in PresetSequencer. Dec 27, 2019
test Fix audio test for cases where default input device is different to d… Dec 9, 2019
.gitattributes More cleanup for deprecated classes. Apr 23, 2019
.gitignore
.gitmodules
.travis.yml
CMakeLists.txt
allosystem_diff.txt file organization: more similar to allocore Jul 4, 2019
readme.md

readme.md

Allolib C/C++ Libraries {#mainpage}

Developed by:

AlloSphere Research Group

allolib is a fork of AlloSystem, maintained in separate repository.

University of California, Santa Barbara

Build Status Build status

Documentation

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

Installing Allolib

Dependencies

Allolib depends on Cmake version 3.8 (as the build tool), OpenGL and glew. See platform specific instructions below.

Windows

There are two paths for Windows installation. One through Visual Studio and one through the Chocolatey package manager.

For installation through Visual Studio:

  1. Install Visual Studio 2017 Community Edition from https://visualstudio.microsoft.com/downloads/

  2. During installation options:

    a. Install "Desktop development with C++" workload

    b. Install Individual components: C++/CLI support, Git for Windows, Visual C++ Tools for Cmake

For installation through Chocolatey:

  • Install Chocolatey: Aim your browser at https://chocolatey.org/install. Follow the directions there to install Chocolatey. Wait for this to finish before moving on.
  • Use the choco command to install a C++ compiler. Open cmd.exe (Command Prompt) as administrator and run this command: choco install -y visualstudio2017buildtools visualstudio2017-workload-vctools
  • Use the choco command to install some software. Open cmd.exe (Command Prompt) as administrator and run this command: choco install -y git git-lfs cmake graphviz doxygen atom vscode
  • Install libsndfile: Aim your browser at http://www.mega-nerd.com/libsndfile/#Download. Download and install the 64-bit version: libsndfile-1.0.xx-w64-setup.exe.

macOS

  • Install Xcode: Open the App Store app. Search for "xcode". Install the first result. Wait for this to finish before moving on.
  • Install Homebrew: Open the Terminal app. Aim your browser at https://brew.sh. Copy and paste the text of the install command into the Terminal app.
  • Use the brew command to install some software. In the Terminal app, run this command: brew install git git-lfs cmake libsndfile

Ubuntu/Debian

sudo apt install build-essential git git-lfs cmake libsndfile1-dev libassimp-dev

allolib requires gcc >= 7. If you need to build on older versions, you can use a ppa to get gcc:

sudo -E apt-add-repository -y "ppa:ubuntu-toolchain-r/test"
sudo apt update
sudo -E apt-get install gcc-8 g++-8

Building library and running examples

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

git clone https://github.com/AlloSphere-Research-Group/allolib
cd allolib
git submodule update --recursive --init
mkdir build
cd build
cmake .. -DBUILD_EXAMPLES=1
cmake . --build

The library will be built in build/lib.

Building aplications with allolib

There are two options provided to build allolib applications. The first is allolib_playground that is great for prototyping single file applications and for exploring the examples. For more complex projects with multiple source files and dependencies, use allotemplate

Extensions

Allolib provides an extension mechanism for libraries that have large or platform dependent dependencies. The stable set of extensions can be found in the al_ext repo. The allotemplate repo linked above shows how to integrate them. al_ext is a separate repo that depends on the allolib library and provides cmake facilities for easy integration with it.

You can’t perform that action at this time.