This repository is the successor to apothecary. It is the central place where all openFrameworks dependencies are built and managed, and downloaded on-demand by openFrameworks projects.
All packages are built and served completely automated with CI, so all you have to do is commit something and wait. The package is automatically built and uploaded into the latest Release.
Following architectures are supported:
| Architecture | Description |
|---|---|
| x64 | Your typical PC architecture, synonymous to x86_64 or amd64 |
| armv7 | Typical 32-bit ARM architecture with Hardware-Float, synonymous to aarch32. Most RPI's use this, except for RPI Zero, which uses armv6 and does not support Hardware-Float |
| aarch64 | 64-bit ARM architecture, synonymous to armv8. RPI 4 and onwards support this architecture (with the correct OS). |
Currently, armv6 is not provided as it is unlikely that anyone would want to run OpenFrameworks on a Raspberry PI Zero, as it has very limited processing power and is unlikely to be enough for an OpenFrameworks application anyways.
See: https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads
https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.1
Also, cross-compiled packages like armv7 and aarch64 are only available for GCC compilers.
| Status | |
|---|---|
| Windows 64 | Done |
| Windows ARM64 | Done |
| Windows ARM64EC | |
| Linux x86_64 | Done |
| Linux armv6 | Not Planned |
| Linux armv7 | Done |
| Linux aarch64 | Done |
| MacOS 64 | |
| MacOS ARM64 | |
| Emscripten | |
| iOS ARM64 | |
| iOS X86_64 SIM | |
| iOS ARM64 SIM | |
| tvOS ARM64 | |
| tvOS X86_64 SIM | |
| tvOS ARM64 SIM | |
| XROS ARM64 | |
| XROS X86_64 SIM | |
| XROS ARM64 SIM | |
| MAC CATOS ARM64 | |
| MAC CATOS x86_64 | |
| Android ARM64 | |
| Android X86_64 | |
| Android X86 | |
| Android ARMV7 |
All prebuilt binary packages can be found at:
https://github.com/openframeworks/packages/releases/tag/latest
They are intended to be downloaded by scripts, not users.
You can build a single package locally, using the compiler that is being picked up by CMake.
python build.py <package_name>
# Example: python build.py freeimageThe selected package will be built locally using the compiler chosen by CMake. Thus, you can only test packages for the compiler and architecture you are running on. See the workflow files to see what environment variables to set, if you are on Linux and want to test cross-compilation locally.
When the package finished building, an archive package consisting of all binaries, headers and CMake files will be generated in an out/ directory.
You need a working Ninja backend.
Some packages also include a requirements.txt file which contains pip dependencies. You might need to manually install these too.