Default linker can be set with DEFAULT_LINKER in options.
Packages can influence linker selection both by positive and/or
negative PKG_BUILD_FLAGS, eg +bfd or -gold.
Positive build flags take priority over the default linker so eg
DEFAULT_LINKER="gold" and PKG_BUILD_FLAGS="+bfd" will select bfd.
Negative flags mean a specific linker should not be used, eg -gold
prevents using gold.
If the default linker is disabled via a build flag then any other
available linker will be used.
Optional linkers like gold have to be enabled with eg GOLD_SUPPORT="yes"
in options. If an optional linker is not enabled it won't be a candidate
for linker selection. So eg "+mold" will have no effect if MOLD_SUPPORT
isn't set to "yes".
Signed-off-by: Matthias Reichl <hias@horus.com>
was:
- OpenGL (GLX) support (provider): no (no)
- OpenGL ES support (provider): yes (mesa)
- Vulkan API support (provider): no (no)
is:
- OpenGL (GLX) support (provider): no
- OpenGL ES support (provider): yes (mesa)
- Vulkan API support (provider): no
- clean up
- tweaks for show_config
- default to `OPENGL/OPENGLES=no` if not set
- sort `GRAPHIC_DRIVERS` & list them for all projects not just x11
- moved video acceleration out of graphic config
FUNCNAME[0] is a bash builtin that corresponds to the name of the currently executing
function. Functions called in bare scripts are in the main() function. Bare scripts
being sourced are in the source() function.
Signed-off-by: Ian Leonard <antonlacon@gmail.com>
Order is roughly:
How is the buildsystem for the image set up
What hardware support is being added
What filesystems will be supported
What Network services are available
Who is providing the graphics and their setup
How does it boot / login
Distribution configuration
Signed-off-by: Ian Leonard <antonlacon@gmail.com>
Split Kodi configuration messages into hardware / software sections. Hardware is how
other software is being built to accomodate Kodi needs (ie what provides video accel).
Software is the configure options to Kodi.
Kodi version just outputs the velue of $MEDIACENTER, which will always be "kodi".
Change to who the "upstream" is for the version of Kodi we're using is instead.
Signed-off-by: Ian Leonard <antonlacon@gmail.com>
This reverts commit 3b5986704e002602cf72c9e34206d2938dcc0a0b.
The config shell is set as an interpreter in libtool scripts
and as Linux has a hard limit of 127 bytes on the first line
in scripts (including the hashbang) this causes the build to
fail with a "bad interpreter" error if the path to the config
shell exceeds this limit.
These errors were first noticed on jenkins builds but can be
easily reproduced by building LibreELEC in a longer build dir.
eg RPi2 clean build failing on libtool invocation in kmod build:
./doltlibtool: /home/hias/rpi/libreelec-testing-with-a-long-directory-path-as-on-jenkins/build.LibreELEC-RPi2.arm-9.0-devel/kmod-24/.x86_64-linux-gnu/libtool: /home/hias/rpi/libreelec-testing-with-a-long-directory-path-as-on-jenkins/build.LibreELEC-RPi2.arm-9.0-devel/toolchain/bin/d: bad interpreter: No such file or directory
Signed-off-by: Matthias Reichl <hias@horus.com>
project or device options
this has been added at the end of the virtual debug package as
this is the last point in the build system that any packages are
compiled before images are created
