2f0a222ef4
linux/webos - tools/depends/target testing the makefile setup - tests x64/arm/aarch64 freebsd - tests system ffmpeg osx x64 - test explicit ENABLE_INTERNAL_FFMPEG Other unix - tests search and fallback for KODI_DEPENDSBUILD auto build |
||
|---|---|---|
| .. | ||
| build-aux | ||
| m4 | ||
| native | ||
| pre-depends | ||
| target | ||
| .gitignore | ||
| Makefile | ||
| Makefile.include.in | ||
| README.md | ||
| bootstrap | ||
| configure.ac | ||
| download-files.include | ||
| xbmc-addons.include | ||
README.md
Kodi's Unified Depends Build System
This builds native tools and library dependencies for platforms that do not provide them. It is used on our continuous integration system, jenkins. A nice side effect is that it allows us to use the same tools and library versions across all platforms.
In terms of build system usage, largest percentage is Autotools, followed by CMake and, in rare cases, hand crafted Makefiles. Tools and libraries versions are picked for a reason. If you feel the urge to start bumping them, be prepared for robust testing. Some tools and libraries need patching, most do not.
That said, we try to stay fairly current with used versions and send patches upstream whenever possible.
-
Autotools driven tools and libraries tend to just work provided the author(s) followed proper Autotools format. Execute
./bootstrap, followed by./configure --[...]and you're all set. If./configure --[...]gives you problems, try./autoreconf -vifbefore./configure --[...]. Some authors do silly things and only aconfig.sitecan correct the errors. Watch for this in the config.site(.in) file(s). It is the only way to handle bad Autotools behaviour. -
CMake driven tools and libraries also tend to just work. Setup CMake flags correctly and go. On rare cases, you might need to diddle the native CMake setup.
-
Hand crafted Makefiles driven tools and libraries typically require manual sed tweaks or patching. May give you nightmares.
Usage Examples
Paths below are examples. If you want to build Kodi, follow our build guides.
All platforms
./bootstrap
Darwin
macOS (x86_64)
./configure --host=x86_64-apple-darwin
iOS (arm64)
./configure --host=aarch64-apple-darwin
tvOS
./configure --host=aarch64-apple-darwin --with-platform=tvos
[!NOTE]
You can target the same--prefix=path. Each setup will be done in an isolated directory. The last configure/make you do is the one used for Kodi/Xcode.
Android
arm
./configure --with-tarballs=$HOME/android-tools/xbmc-tarballs --host=arm-linux-androideabi --with-sdk-path=$HOME/android-tools/android-sdk-linux --with-ndk-path=$HOME/android-tools/android-ndk-r20 --prefix=$HOME/android-tools/xbmc-depends
aarch64
./configure --with-tarballs=$HOME/android-tools/xbmc-tarballs --host=aarch64-linux-android --with-sdk-path=$HOME/android-tools/android-sdk-linux --with-ndk-path=$HOME/android-tools/android-ndk-r20 --prefix=$HOME/android-tools/xbmc-depends
x86
./configure --with-tarballs=$HOME/android-tools/xbmc-tarballs --host=i686-linux-android --with-sdk-path=$HOME/android-tools/android-sdk-linux --with-ndk-path=$HOME/android-tools/android-ndk-r20 --prefix=$HOME/android-tools/xbmc-depends
x86_64
./configure --with-tarballs=$HOME/android-tools/xbmc-tarballs --host=x86_64-linux-android --with-sdk-path=$HOME/android-tools/android-sdk-linux --with-ndk-path=$HOME/android-tools/android-ndk-r20 --prefix=$HOME/android-tools/xbmc-depends
[!NOTE]
Android x86 and x86_64 are not maintained and are not 100% sure that everything works correctly!
Linux
ARM (codesourcery/lenaro/etc)
./configure --with-toolchain=/opt/toolchains/my-example-toolchain/ --prefix=/opt/xbmc-deps --host=arm-linux-gnueabi --with-rendersystem=gles
webos (buildroot-nc4)
./configure --with-toolchain=/opt/toolchains/arm-webos-linux-gnueabi_sdk-buildroot --prefix=/opt/xbmc-deps --host=arm-webos-linux-gnueabi
Native
./configure --with-toolchain=/usr --prefix=/opt/xbmc-deps --host=x86_64-linux-gnu --with-rendersystem=gl
Cross compiling is a PITA.