From 9fc8b732737f139d3e466510d75668ab45578960 Mon Sep 17 00:00:00 2001 From: manuel Date: Tue, 8 Mar 2016 21:02:53 +0100 Subject: sync with upstream --- project/cmake/addons/README | 28 +++++++++++++++++++++++----- 1 file changed, 23 insertions(+), 5 deletions(-) (limited to 'project/cmake/addons/README') diff --git a/project/cmake/addons/README b/project/cmake/addons/README index b901bb7..a0f2c32 100644 --- a/project/cmake/addons/README +++ b/project/cmake/addons/README @@ -1,7 +1,8 @@ KODI ADDONS =========== This directory contains the cmake-based buildsystem for addons. It looks into -the "addons" sub-directory and parses all *.txt files recursively. Each addon +the directory pointed to by the ADDONS_DEFINITION_DIR option (which defaults to +the "addons" sub-directory) and parses all *.txt files recursively. Each addon must have its own .txt file in a separate sub-directory which must follow one of the defined format: @@ -22,13 +23,26 @@ are: * platforms.txt: List of platforms to build an addon for (or "all"). It is also supported to specify negated platforms with a leading exclamation mark (i), e.g. "!windows". - Available platforms are: linux, windows, darwin, ios, android, rbpi + Available platforms are: linux, windows, osx, ios, android, rbpi, freebsd + +ATTENTION: If no addon definitions could be found the buildsystem assumes that + the bootstrapping of the addon definition repositories hasn't been + performed yet and automatically executes the addon bootstrapping + buildsystem located in the "bootstrap" sub-directory with the default + settings (i.e. all addons from all pre-defined addon definition + repositories are bootstrapped into the directory pointed to by the + ADDONS_DEFINITION_DIR option). The buildsystem uses the following variables (which can be passed into it when executing cmake with the -D= option) to e.g. access specific paths: - * ADDONS_TO_BUILD is a quoted, space delimited list of s that - you want to build (default is "all"). + * ADDONS_TO_BUILD has two variations, which are tested in order: + - a quoted, space delimited list of s that + you want to build (default is "all"). + - a regular expression that every is matched against + e.g.: ADDONS_TO_BUILD=pvr.* to build all pvr addons + * ADDONS_DEFINITION_DIR points to the directory containing the definitions + for the addons to be built. * ADDON_SRC_PREFIX can be used to override the addon repository location. It must point to the locally available parent directory of the addon(s) to build will be appended to this path automatically @@ -45,11 +59,15 @@ specific paths: absolute representation of ../../.. starting from this directory). * BUILD_DIR points to the directory where the addons and their dependencies will be downloaded and built. - * PACKAGE_ZIP=1 will mean the add-ons will be 'packaged' into a common folder, + * PACKAGE_ZIP=ON means that the add-ons will be 'packaged' into a common folder, rather than being placed in /lib/kodi/addons and /share/kodi/addons. + * PACKAGE_DIR points to the directory where the ZIP archived addons will be + stored after they have been packaged (defaults to /zips) * ARCH_DEFINES specifies the platform-specific C/C++ preprocessor defines (defaults to empty). + * ADDON_TARBALL_CACHING specifies whether downloaded addon source tarballs + should be cached or not (defaults to ON). The buildsystem makes some assumptions about the environment which must be met by whoever uses it: -- cgit v1.2.3