The devkit project consists of several individual documentation files to explain how to build most of libraries we require in our applications.
All libraries are built as shared. In contrast to many package managers, devkit does not build as much as features and only keep what we needs. For example libsdl-image is only built with PNG support.
|Visual Studio||x64||Debug and Release in separate directories|
|Android||armeabi-v7a, arm64-v8a, x86, x86-64||Release||Target android-24 API level|
Prebuilt kits are built under the following paths:
- Visual Studio: C:/pkg/vs/release|debug
- Android: /opt/android
The following libraries are supported
|libogg||Medium||Opensource video/audio container||libogg.md|
|libpng||Medium||PNG image file||libpng.md|
|libsdl||High||Simple Directmedia Layer||http://libsdl.org||libsdl.md|
|libsdl-image||High||Image addon for SDL2||libsdl-image.md|
|libsdl-mixer||High||Music addon for SDL2||libsdl-mixer.md|
|libsdl-ttf||High||Font addon for SDL2||libsdl-ttf.md|
|libvorbis||Medium||Opensource audio stream||libvorbis.md|
Why not vcpkg?¶
I did a try with it and I was not able to build some of the required packages. Also, I don't really like the black magic that vcpkg does. I want to have full control of what I'm building with as less dependencies possible.
I recommend using MSYS2 which does a perfect job maintaining a high number of packages with mintty.