diff options
Diffstat (limited to 'bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample')
76 files changed, 0 insertions, 15754 deletions
diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/linaro-gcc/bsp/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/linaro-gcc/bsp/bblayers.conf deleted file mode 100644 index 96ff8ada..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/linaro-gcc/bsp/bblayers.conf +++ /dev/null @@ -1,16 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-linaro-toolchain \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/linaro-gcc/bsp/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/linaro-gcc/bsp/local-wayland.conf deleted file mode 100644 index 51d1e75f..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/linaro-gcc/bsp/local-wayland.conf +++ /dev/null @@ -1,271 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "ebisu" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# Linaro GCC -GCCVERSION = "linaro-7.2" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# for Wayland/Weston weston-laucher -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" - -# Mask the wayland related to GFX -BBMASK .= "|gles-user-module|kernel-module-gles|wayland-kms|libgbm" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Mask the gstreamer recipe for MMP -BBMASK .= "|meta-renesas/meta-rcar-gen3/recipes-multimedia/gstreamer" - -# Add for gstreamer plugins ugly -LICENSE_FLAGS_WHITELIST = "commercial" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Configuration for USB 3.0 -MACHINE_FEATURES_append = " usb3" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/linaro-gcc/bsp/local.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/linaro-gcc/bsp/local.conf deleted file mode 100644 index 52a23fe8..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/linaro-gcc/bsp/local.conf +++ /dev/null @@ -1,264 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "ebisu" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# Linaro GCC -GCCVERSION = "linaro-7.2" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Mask graphic Pkgs -BBMASK .= "|gles-user-module|kernel-module-gles|wayland-kms|libgbm" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Enable pam distro feature -DISTRO_FEATURES_append = " pam" - -# Configuration for USB 3.0 -MACHINE_FEATURES_append = " usb3" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/linaro-gcc/gfx-only/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/linaro-gcc/gfx-only/bblayers.conf deleted file mode 100644 index 96ff8ada..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/linaro-gcc/gfx-only/bblayers.conf +++ /dev/null @@ -1,16 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-linaro-toolchain \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/linaro-gcc/gfx-only/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/linaro-gcc/gfx-only/local-wayland.conf deleted file mode 100644 index 83d8eb2e..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/linaro-gcc/gfx-only/local-wayland.conf +++ /dev/null @@ -1,277 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "ebisu" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# Linaro GCC -GCCVERSION = "linaro-7.2" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Enable Gfx Pkgs -MACHINE_FEATURES_append = " gsx" -MULTI_PROVIDER_WHITELIST += "virtual/libgl virtual/egl virtual/libgles1 virtual/libgles2" - -# for Wayland/Weston -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" -PREFERRED_PROVIDER_virtual/libgles1 = "" -PREFERRED_PROVIDER_virtual/libgles2 = "gles-user-module" -PREFERRED_PROVIDER_virtual/egl = "libegl" -PREFERRED_PROVIDER_virtual/libgl = "" -PREFERRED_PROVIDER_virtual/mesa = "" -PREFERRED_PROVIDER_libgbm = "libgbm" -PREFERRED_PROVIDER_libgbm-dev = "libgbm" -BBMASK .= "|mesa-gl" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Add for gstreamer plugins ugly -LICENSE_FLAGS_WHITELIST = "commercial" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Configuration for USB 3.0 -MACHINE_FEATURES_append = " usb3" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/linaro-gcc/mmp/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/linaro-gcc/mmp/bblayers.conf deleted file mode 100644 index 96ff8ada..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/linaro-gcc/mmp/bblayers.conf +++ /dev/null @@ -1,16 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-linaro-toolchain \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/linaro-gcc/mmp/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/linaro-gcc/mmp/local-wayland.conf deleted file mode 100644 index 2ad6044f..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/linaro-gcc/mmp/local-wayland.conf +++ /dev/null @@ -1,383 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "ebisu" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# Linaro GCC -GCCVERSION = "linaro-7.2" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Enable Gfx Pkgs -MACHINE_FEATURES_append = " gsx" -MULTI_PROVIDER_WHITELIST += "virtual/libgl virtual/egl virtual/libgles1 virtual/libgles2" - -# for Wayland/Weston -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" -PREFERRED_PROVIDER_virtual/libgles1 = "" -PREFERRED_PROVIDER_virtual/libgles2 = "gles-user-module" -PREFERRED_PROVIDER_virtual/egl = "libegl" -PREFERRED_PROVIDER_virtual/libgl = "" -PREFERRED_PROVIDER_virtual/mesa = "" -PREFERRED_PROVIDER_libgbm = "libgbm" -PREFERRED_PROVIDER_libgbm-dev = "libgbm" -BBMASK .= "|mesa-gl" - -# Enable Multimedia features -MACHINE_FEATURES_append = " multimedia" - -# for gstreamer omx plugins -LICENSE_FLAGS_WHITELIST = "commercial" -# for mmp test program -DISTRO_FEATURES_append = " mm-test" - -# for weston v4l2 renderer -#DISTRO_FEATURES_append = " v4l2-renderer" - -# OMX H263 decoder library for Linux (RTM0AC0000XV263D30SL41C) -#DISTRO_FEATURES_append = " h263dec_lib" - -# OMX H264 decoder library for Linux (RTM0AC0000XV264D30SL41C) -DISTRO_FEATURES_append = " h264dec_lib" - -# OMX H264 encoder library for Linux (RTM0AC0000XV264E30SL41C) -#DISTRO_FEATURES_append = " h264enc_lib" - -# OMX H265 decoder library for Linux (RTM0AC0000XV265D30SL41C) -#DISTRO_FEATURES_append = " h265dec_lib" - -# OMX MPEG2 decoder library for Linux (RTM0AC0000XVM2VD30SL41C) -#DISTRO_FEATURES_append = " mpeg2dec_lib" - -# OMX Media Component MPEG4 Decoder Library for Linux (RTM0AC0000XVM4VD30SL41C) -#DISTRO_FEATURES_append = " mpeg4dec_lib" - -# OMX Media Component VC-1 Decoder Library for Linux (RTM0AC0000XVVC1D30SL41C) -#DISTRO_FEATURES_append = " vc1dec_lib" - -# OMX Media Component DivXD Decoder Library for Linux (RTM0AC0000XVDVXD30SL41C) -#DISTRO_FEATURES_append = " divxdec_lib" - -# OMX Media Component RealVideo Decoder Library for Linux (RTM0AC0000XVRLVD30SL41C) -#DISTRO_FEATURES_append = " rvdec_lib" - -# OMX Media Component ALAC Decoder Library for Linux (RTM0AC0000XAALAD30SL41C) -#DISTRO_FEATURES_append = " alacdec_lib" - -# OMX Media Component FLAC Decoder Library for Linux (RTM0AC0000XAFLAD30SL41C) -#DISTRO_FEATURES_append = " flacdec_lib" - -# OMX AAC-LC decoder library for Linux (RTM0AC0000XAAACD30SL41C), -# AAC-LC 2ch decoder middleware library for Linux (RTM0AC0000ADAACMZ1SL41C) -DISTRO_FEATURES_append = " aaclcdec_lib" -DISTRO_FEATURES_append = " aaclcdec_mdw" - -# OMX aacPlus V2 decoder library for Linux (RTM0AC0000XAAAPD30SL41C), -# aacPlus V2 decoder middleware library for Linux (RTM0AC0000ADAAPMZ1SL41C) -#DISTRO_FEATURES_append = " aacpv2dec_lib" -#DISTRO_FEATURES_append = " aacpv2dec_mdw" - -# OMX MP3 decoder library for Linux (RTM0AC0000XAMP3D30SL41C), -# MP3 decoder middleware library for Linux (RTM0AC0000ADMP3MZ1SL41C) -#DISTRO_FEATURES_append = " mp3dec_lib" -#DISTRO_FEATURES_append = " mp3dec_mdw" - -# OMX WMA decoder library for Linux (RTM0AC0000XAWMAD30SL41C), -# WMA decoder middleware library for Linux (RTM0AC0000ADWMAMZ1SL41C) -#DISTRO_FEATURES_append = " wmadec_lib" -#DISTRO_FEATURES_append = " wmadec_mdw" - -# OMX AAC-LC encoder library for Linux (RTM0AC0000XAAACE30SL41C) -# AAC-LC encoder middleware library for Linux (RTM0AC0000AEAACMZ1SL41C) -#DISTRO_FEATURES_append = " aaclcenc_lib" -#DISTRO_FEATURES_append = " aaclcenc_mdw" - -# OMX Dolby(R) Digital decoder library for Linux (RTM0AC0000XADD5D30SL41C), -# Dolby(R) Digital decoder middleware library for Linux (RTM0AC0000ADDD5MZ1SL41C) -#DISTRO_FEATURES_append = " dddec_lib" -#DISTRO_FEATURES_append = " dddec_mdw" - -# OMX Media Component VP8 Decoder Library for Linux (RTM0AC0000XVVP8D30SL41C) -#DISTRO_FEATURES_append = " vp8dec_lib" - -# OMX Media Component VP8 Encoder Library for Linux (RTM0AC0000XVVP8E30SL41C) -#DISTRO_FEATURES_append = " vp8enc_lib" - -# OMX Media Component VP9 Decoder Library for Linux (RTM0AC0000XVVP9D30SL41C) -#DISTRO_FEATURES_append = " vp9dec_lib" - -# CMS Basic Color Management Middleware for Linux (RTM0AC0000JRCMBCV0SL41C) -#DISTRO_FEATURES_append = " cmsbcm" - -# CMS CMM3 Backlight Control Middleware for Linux (RTM0AC0000JRCMBLC0SL41C) -#DISTRO_FEATURES_append = " cmsblc" - -# CMS VSP2 Dynamic Gamma Correction Middleware for Linux (RTM0AC0000JRCMDGV0SL41C) -#DISTRO_FEATURES_append = " cmsdgc" - -# DVD Core-Middleware for Linux (RTM0RC0000XDVDC301SL41C) -# DVD Encryption Library for Linux (RTM0RC0000XDVDF301SL41C) -#DISTRO_FEATURES_append = " dvd" -#DISTRO_FEATURES_append = " dvd_encryption_library" - -# ADSP Driver for Linux (RCG3AHPDL4101ZDO) -# ADSP Interface for Linux (RCG3AHIFL4101ZDP) -# ADSP Framework (RCG3AHFWN0201ZDP) -#DISTRO_FEATURES_append = " adsp" - -# AVB Software Package for Linux -#DISTRO_FEATURES_append = " avb" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Evaluation packages -#DISTRO_FEATURES_append = " use_eva_pkg" - -# Configuration for ivi-shell and ivi-extension -#DISTRO_FEATURES_append = " ivi-shell" - -# Configuration for USB 3.0 -MACHINE_FEATURES_append = " usb3" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/poky-gcc/bsp/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/poky-gcc/bsp/bblayers.conf deleted file mode 100644 index 3b2c068a..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/poky-gcc/bsp/bblayers.conf +++ /dev/null @@ -1,15 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - ${TOPDIR}/../meta-linaro/meta-optee \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/poky-gcc/bsp/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/poky-gcc/bsp/local-wayland.conf deleted file mode 100644 index b9fde5c6..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/poky-gcc/bsp/local-wayland.conf +++ /dev/null @@ -1,279 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone-yocto" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "ebisu" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - -# -# Yocto Project SState Mirror -# -# The Yocto Project has prebuilt artefacts available for its releases, you can enable -# use of these by uncommenting the following line. This will mean the build uses -# the network to check for artefacts at the start of builds, which does slow it down -# equally, it will also speed up the builds by not having to build things if they are -# present in the cache. It assumes you can download something faster than you can build it -# which will depend on your network. -# -#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH" - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl2-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl2-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl2-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# for Wayland/Weston weston-laucher -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" - -# Mask the wayland related to GFX -BBMASK .= "|gles-user-module|kernel-module-gles|wayland-kms|libgbm" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Mask the gstreamer recipe for MMP -BBMASK .= "|meta-renesas/meta-rcar-gen3/recipes-multimedia/gstreamer" - -# Add for gstreamer plugins ugly -LICENSE_FLAGS_WHITELIST = "commercial" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Configuration for USB 3.0 -MACHINE_FEATURES_append = " usb3" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/poky-gcc/bsp/local.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/poky-gcc/bsp/local.conf deleted file mode 100644 index bcbcef15..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/poky-gcc/bsp/local.conf +++ /dev/null @@ -1,272 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone-yocto" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "ebisu" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - -# -# Yocto Project SState Mirror -# -# The Yocto Project has prebuilt artefacts available for its releases, you can enable -# use of these by uncommenting the following line. This will mean the build uses -# the network to check for artefacts at the start of builds, which does slow it down -# equally, it will also speed up the builds by not having to build things if they are -# present in the cache. It assumes you can download something faster than you can build it -# which will depend on your network. -# -#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH" - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl2-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl2-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl2-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Mask graphic Pkgs -BBMASK .= "|gles-user-module|kernel-module-gles|wayland-kms|libgbm" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Enable pam distro feature -DISTRO_FEATURES_append = " pam" - -# Configuration for USB 3.0 -MACHINE_FEATURES_append = " usb3" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/poky-gcc/gfx-only/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/poky-gcc/gfx-only/bblayers.conf deleted file mode 100644 index 882db523..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/poky-gcc/gfx-only/bblayers.conf +++ /dev/null @@ -1,15 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/poky-gcc/gfx-only/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/poky-gcc/gfx-only/local-wayland.conf deleted file mode 100644 index 150e894f..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/poky-gcc/gfx-only/local-wayland.conf +++ /dev/null @@ -1,285 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone-yocto" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "ebisu" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - -# -# Yocto Project SState Mirror -# -# The Yocto Project has prebuilt artefacts available for its releases, you can enable -# use of these by uncommenting the following line. This will mean the build uses -# the network to check for artefacts at the start of builds, which does slow it down -# equally, it will also speed up the builds by not having to build things if they are -# present in the cache. It assumes you can download something faster than you can build it -# which will depend on your network. -# -#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH" - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl2-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl2-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl2-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Enable Gfx Pkgs -MACHINE_FEATURES_append = " gsx" -MULTI_PROVIDER_WHITELIST += "virtual/libgl virtual/egl virtual/libgles1 virtual/libgles2" - -# for Wayland/Weston -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" -PREFERRED_PROVIDER_virtual/libgles1 = "" -PREFERRED_PROVIDER_virtual/libgles2 = "gles-user-module" -PREFERRED_PROVIDER_virtual/egl = "libegl" -PREFERRED_PROVIDER_virtual/libgl = "" -PREFERRED_PROVIDER_virtual/mesa = "" -PREFERRED_PROVIDER_virtual/libgbm = "libgbm" -PREFERRED_PROVIDER_libgbm-dev = "libgbm" -BBMASK .= "|mesa-gl" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Add for gstreamer plugins ugly -LICENSE_FLAGS_WHITELIST = "commercial" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Configuration for USB 3.0 -MACHINE_FEATURES_append = " usb3" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/poky-gcc/mmp/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/poky-gcc/mmp/bblayers.conf deleted file mode 100644 index 882db523..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/poky-gcc/mmp/bblayers.conf +++ /dev/null @@ -1,15 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/poky-gcc/mmp/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/poky-gcc/mmp/local-wayland.conf deleted file mode 100644 index 0f606bf7..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/ebisu/poky-gcc/mmp/local-wayland.conf +++ /dev/null @@ -1,391 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone-yocto" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "ebisu" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - -# -# Yocto Project SState Mirror -# -# The Yocto Project has prebuilt artefacts available for its releases, you can enable -# use of these by uncommenting the following line. This will mean the build uses -# the network to check for artefacts at the start of builds, which does slow it down -# equally, it will also speed up the builds by not having to build things if they are -# present in the cache. It assumes you can download something faster than you can build it -# which will depend on your network. -# -#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH" - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl2-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl2-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl2-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Enable Gfx Pkgs -MACHINE_FEATURES_append = " gsx" -MULTI_PROVIDER_WHITELIST += "virtual/libgl virtual/egl virtual/libgles1 virtual/libgles2" - -# for Wayland/Weston -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" -PREFERRED_PROVIDER_virtual/libgles1 = "" -PREFERRED_PROVIDER_virtual/libgles2 = "gles-user-module" -PREFERRED_PROVIDER_virtual/egl = "libegl" -PREFERRED_PROVIDER_virtual/libgl = "" -PREFERRED_PROVIDER_virtual/mesa = "" -PREFERRED_PROVIDER_virtual/libgbm = "libgbm" -PREFERRED_PROVIDER_libgbm-dev = "libgbm" -BBMASK .= "|mesa-gl" - -# Enable Multimedia features -MACHINE_FEATURES_append = " multimedia" - -# for gstreamer omx plugins -LICENSE_FLAGS_WHITELIST = "commercial" -# for mmp test program -DISTRO_FEATURES_append = " mm-test" - -# for weston v4l2 renderer -#DISTRO_FEATURES_append = " v4l2-renderer" - -# OMX H263 decoder library for Linux (RTM0AC0000XV263D30SL41C) -#DISTRO_FEATURES_append = " h263dec_lib" - -# OMX H264 decoder library for Linux (RTM0AC0000XV264D30SL41C) -DISTRO_FEATURES_append = " h264dec_lib" - -# OMX H264 encoder library for Linux (RTM0AC0000XV264E30SL41C) -#DISTRO_FEATURES_append = " h264enc_lib" - -# OMX H265 decoder library for Linux (RTM0AC0000XV265D30SL41C) -#DISTRO_FEATURES_append = " h265dec_lib" - -# OMX MPEG2 decoder library for Linux (RTM0AC0000XVM2VD30SL41C) -#DISTRO_FEATURES_append = " mpeg2dec_lib" - -# OMX Media Component MPEG4 Decoder Library for Linux (RTM0AC0000XVM4VD30SL41C) -#DISTRO_FEATURES_append = " mpeg4dec_lib" - -# OMX Media Component VC-1 Decoder Library for Linux (RTM0AC0000XVVC1D30SL41C) -#DISTRO_FEATURES_append = " vc1dec_lib" - -# OMX Media Component DivXD Decoder Library for Linux (RTM0AC0000XVDVXD30SL41C) -#DISTRO_FEATURES_append = " divxdec_lib" - -# OMX Media Component RealVideo Decoder Library for Linux (RTM0AC0000XVRLVD30SL41C) -#DISTRO_FEATURES_append = " rvdec_lib" - -# OMX Media Component ALAC Decoder Library for Linux (RTM0AC0000XAALAD30SL41C) -#DISTRO_FEATURES_append = " alacdec_lib" - -# OMX Media Component FLAC Decoder Library for Linux (RTM0AC0000XAFLAD30SL41C) -#DISTRO_FEATURES_append = " flacdec_lib" - -# OMX AAC-LC decoder library for Linux (RTM0AC0000XAAACD30SL41C), -# AAC-LC 2ch decoder middleware library for Linux (RTM0AC0000ADAACMZ1SL41C) -DISTRO_FEATURES_append = " aaclcdec_lib" -DISTRO_FEATURES_append = " aaclcdec_mdw" - -# OMX aacPlus V2 decoder library for Linux (RTM0AC0000XAAAPD30SL41C), -# aacPlus V2 decoder middleware library for Linux (RTM0AC0000ADAAPMZ1SL41C) -#DISTRO_FEATURES_append = " aacpv2dec_lib" -#DISTRO_FEATURES_append = " aacpv2dec_mdw" - -# OMX MP3 decoder library for Linux (RTM0AC0000XAMP3D30SL41C), -# MP3 decoder middleware library for Linux (RTM0AC0000ADMP3MZ1SL41C) -#DISTRO_FEATURES_append = " mp3dec_lib" -#DISTRO_FEATURES_append = " mp3dec_mdw" - -# OMX WMA decoder library for Linux (RTM0AC0000XAWMAD30SL41C), -# WMA decoder middleware library for Linux (RTM0AC0000ADWMAMZ1SL41C) -#DISTRO_FEATURES_append = " wmadec_lib" -#DISTRO_FEATURES_append = " wmadec_mdw" - -# OMX AAC-LC encoder library for Linux (RTM0AC0000XAAACE30SL41C) -# AAC-LC encoder middleware library for Linux (RTM0AC0000AEAACMZ1SL41C) -#DISTRO_FEATURES_append = " aaclcenc_lib" -#DISTRO_FEATURES_append = " aaclcenc_mdw" - -# OMX Dolby(R) Digital decoder library for Linux (RTM0AC0000XADD5D30SL41C), -# Dolby(R) Digital decoder middleware library for Linux (RTM0AC0000ADDD5MZ1SL41C) -#DISTRO_FEATURES_append = " dddec_lib" -#DISTRO_FEATURES_append = " dddec_mdw" - -# OMX Media Component VP8 Decoder Library for Linux (RTM0AC0000XVVP8D30SL41C) -#DISTRO_FEATURES_append = " vp8dec_lib" - -# OMX Media Component VP8 Encoder Library for Linux (RTM0AC0000XVVP8E30SL41C) -#DISTRO_FEATURES_append = " vp8enc_lib" - -# OMX Media Component VP9 Decoder Library for Linux (RTM0AC0000XVVP9D30SL41C) -#DISTRO_FEATURES_append = " vp9dec_lib" - -# CMS Basic Color Management Middleware for Linux (RTM0AC0000JRCMBCV0SL41C) -#DISTRO_FEATURES_append = " cmsbcm" - -# CMS CMM3 Backlight Control Middleware for Linux (RTM0AC0000JRCMBLC0SL41C) -#DISTRO_FEATURES_append = " cmsblc" - -# CMS VSP2 Dynamic Gamma Correction Middleware for Linux (RTM0AC0000JRCMDGV0SL41C) -#DISTRO_FEATURES_append = " cmsdgc" - -# DVD Core-Middleware for Linux (RTM0RC0000XDVDC301SL41C) -# DVD Encryption Library for Linux (RTM0RC0000XDVDF301SL41C) -#DISTRO_FEATURES_append = " dvd" -#DISTRO_FEATURES_append = " dvd_encryption_library" - -# ADSP Driver for Linux (RCG3AHPDL4101ZDO) -# ADSP Interface for Linux (RCG3AHIFL4101ZDP) -# ADSP Framework (RCG3AHFWN0201ZDP) -#DISTRO_FEATURES_append = " adsp" - -# AVB Software Package for Linux -#DISTRO_FEATURES_append = " avb" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Evaluation packages -#DISTRO_FEATURES_append = " use_eva_pkg" - -# Configuration for ivi-shell and ivi-extension -#DISTRO_FEATURES_append = " ivi-shell" - -# Configuration for USB 3.0 -MACHINE_FEATURES_append = " usb3" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/bsp/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/bsp/bblayers.conf deleted file mode 100644 index 96ff8ada..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/bsp/bblayers.conf +++ /dev/null @@ -1,16 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-linaro-toolchain \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/bsp/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/bsp/local-wayland.conf deleted file mode 100644 index cfc98c06..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/bsp/local-wayland.conf +++ /dev/null @@ -1,271 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "h3ulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# Linaro GCC -GCCVERSION = "linaro-7.2" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# for Wayland/Weston weston-laucher -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" - -# Mask the wayland related to GFX -BBMASK .= "|gles-user-module|kernel-module-gles|wayland-kms|libgbm" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Mask the gstreamer recipe for MMP -BBMASK .= "|meta-renesas/meta-rcar-gen3/recipes-multimedia/gstreamer" - -# Add for gstreamer plugins ugly -LICENSE_FLAGS_WHITELIST = "commercial" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/bsp/local.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/bsp/local.conf deleted file mode 100644 index c7b7b533..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/bsp/local.conf +++ /dev/null @@ -1,264 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "h3ulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# Linaro GCC -GCCVERSION = "linaro-7.2" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Mask graphic Pkgs -BBMASK .= "|gles-user-module|kernel-module-gles|wayland-kms|libgbm" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Enable pam distro feature -DISTRO_FEATURES_append = " pam" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/gfx-only/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/gfx-only/bblayers.conf deleted file mode 100644 index 96ff8ada..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/gfx-only/bblayers.conf +++ /dev/null @@ -1,16 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-linaro-toolchain \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/gfx-only/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/gfx-only/local-wayland.conf deleted file mode 100644 index 5785f2a2..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/gfx-only/local-wayland.conf +++ /dev/null @@ -1,277 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "h3ulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# Linaro GCC -GCCVERSION = "linaro-7.2" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Enable Gfx Pkgs -MACHINE_FEATURES_append = " gsx" -MULTI_PROVIDER_WHITELIST += "virtual/libgl virtual/egl virtual/libgles1 virtual/libgles2" - -# for Wayland/Weston -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" -PREFERRED_PROVIDER_virtual/libgles1 = "" -PREFERRED_PROVIDER_virtual/libgles2 = "gles-user-module" -PREFERRED_PROVIDER_virtual/egl = "libegl" -PREFERRED_PROVIDER_virtual/libgl = "" -PREFERRED_PROVIDER_virtual/mesa = "" -PREFERRED_PROVIDER_libgbm = "libgbm" -PREFERRED_PROVIDER_libgbm-dev = "libgbm" -BBMASK .= "|mesa-gl" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Add for gstreamer plugins ugly -LICENSE_FLAGS_WHITELIST = "commercial" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/mmp/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/mmp/bblayers.conf deleted file mode 100644 index 96ff8ada..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/mmp/bblayers.conf +++ /dev/null @@ -1,16 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-linaro-toolchain \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/mmp/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/mmp/local-wayland.conf deleted file mode 100644 index 14f4c607..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/mmp/local-wayland.conf +++ /dev/null @@ -1,383 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "h3ulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# Linaro GCC -GCCVERSION = "linaro-7.2" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Enable Gfx Pkgs -MACHINE_FEATURES_append = " gsx" -MULTI_PROVIDER_WHITELIST += "virtual/libgl virtual/egl virtual/libgles1 virtual/libgles2" - -# for Wayland/Weston -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" -PREFERRED_PROVIDER_virtual/libgles1 = "" -PREFERRED_PROVIDER_virtual/libgles2 = "gles-user-module" -PREFERRED_PROVIDER_virtual/egl = "libegl" -PREFERRED_PROVIDER_virtual/libgl = "" -PREFERRED_PROVIDER_virtual/mesa = "" -PREFERRED_PROVIDER_libgbm = "libgbm" -PREFERRED_PROVIDER_libgbm-dev = "libgbm" -BBMASK .= "|mesa-gl" - -# Enable Multimedia features -MACHINE_FEATURES_append = " multimedia" - -# for gstreamer omx plugins -LICENSE_FLAGS_WHITELIST = "commercial" -# for mmp test program -DISTRO_FEATURES_append = " mm-test" - -# for weston v4l2 renderer -#DISTRO_FEATURES_append = " v4l2-renderer" - -# OMX H263 decoder library for Linux (RTM0AC0000XV263D30SL41C) -#DISTRO_FEATURES_append = " h263dec_lib" - -# OMX H264 decoder library for Linux (RTM0AC0000XV264D30SL41C) -DISTRO_FEATURES_append = " h264dec_lib" - -# OMX H264 encoder library for Linux (RTM0AC0000XV264E30SL41C) -#DISTRO_FEATURES_append = " h264enc_lib" - -# OMX H265 decoder library for Linux (RTM0AC0000XV265D30SL41C) -#DISTRO_FEATURES_append = " h265dec_lib" - -# OMX MPEG2 decoder library for Linux (RTM0AC0000XVM2VD30SL41C) -#DISTRO_FEATURES_append = " mpeg2dec_lib" - -# OMX Media Component MPEG4 Decoder Library for Linux (RTM0AC0000XVM4VD30SL41C) -#DISTRO_FEATURES_append = " mpeg4dec_lib" - -# OMX Media Component VC-1 Decoder Library for Linux (RTM0AC0000XVVC1D30SL41C) -#DISTRO_FEATURES_append = " vc1dec_lib" - -# OMX Media Component DivXD Decoder Library for Linux (RTM0AC0000XVDVXD30SL41C) -#DISTRO_FEATURES_append = " divxdec_lib" - -# OMX Media Component RealVideo Decoder Library for Linux (RTM0AC0000XVRLVD30SL41C) -#DISTRO_FEATURES_append = " rvdec_lib" - -# OMX Media Component ALAC Decoder Library for Linux (RTM0AC0000XAALAD30SL41C) -#DISTRO_FEATURES_append = " alacdec_lib" - -# OMX Media Component FLAC Decoder Library for Linux (RTM0AC0000XAFLAD30SL41C) -#DISTRO_FEATURES_append = " flacdec_lib" - -# OMX AAC-LC decoder library for Linux (RTM0AC0000XAAACD30SL41C), -# AAC-LC 2ch decoder middleware library for Linux (RTM0AC0000ADAACMZ1SL41C) -DISTRO_FEATURES_append = " aaclcdec_lib" -DISTRO_FEATURES_append = " aaclcdec_mdw" - -# OMX aacPlus V2 decoder library for Linux (RTM0AC0000XAAAPD30SL41C), -# aacPlus V2 decoder middleware library for Linux (RTM0AC0000ADAAPMZ1SL41C) -#DISTRO_FEATURES_append = " aacpv2dec_lib" -#DISTRO_FEATURES_append = " aacpv2dec_mdw" - -# OMX MP3 decoder library for Linux (RTM0AC0000XAMP3D30SL41C), -# MP3 decoder middleware library for Linux (RTM0AC0000ADMP3MZ1SL41C) -#DISTRO_FEATURES_append = " mp3dec_lib" -#DISTRO_FEATURES_append = " mp3dec_mdw" - -# OMX WMA decoder library for Linux (RTM0AC0000XAWMAD30SL41C), -# WMA decoder middleware library for Linux (RTM0AC0000ADWMAMZ1SL41C) -#DISTRO_FEATURES_append = " wmadec_lib" -#DISTRO_FEATURES_append = " wmadec_mdw" - -# OMX AAC-LC encoder library for Linux (RTM0AC0000XAAACE30SL41C) -# AAC-LC encoder middleware library for Linux (RTM0AC0000AEAACMZ1SL41C) -#DISTRO_FEATURES_append = " aaclcenc_lib" -#DISTRO_FEATURES_append = " aaclcenc_mdw" - -# OMX Dolby(R) Digital decoder library for Linux (RTM0AC0000XADD5D30SL41C), -# Dolby(R) Digital decoder middleware library for Linux (RTM0AC0000ADDD5MZ1SL41C) -#DISTRO_FEATURES_append = " dddec_lib" -#DISTRO_FEATURES_append = " dddec_mdw" - -# OMX Media Component VP8 Decoder Library for Linux (RTM0AC0000XVVP8D30SL41C) -#DISTRO_FEATURES_append = " vp8dec_lib" - -# OMX Media Component VP8 Encoder Library for Linux (RTM0AC0000XVVP8E30SL41C) -#DISTRO_FEATURES_append = " vp8enc_lib" - -# CMS Basic Color Management Middleware for Linux (RTM0AC0000JRCMBCV0SL41C) -#DISTRO_FEATURES_append = " cmsbcm" - -# CMS CMM3 Backlight Control Middleware for Linux (RTM0AC0000JRCMBLC0SL41C) -#DISTRO_FEATURES_append = " cmsblc" - -# CMS VSP2 Dynamic Gamma Correction Middleware for Linux (RTM0AC0000JRCMDGV0SL41C) -#DISTRO_FEATURES_append = " cmsdgc" - -# ISDB-T DTV Software Package for Linux (RTM0RC0000TE020000SL41C) -#DISTRO_FEATURES_append = " dtv" - -# DVD Core-Middleware for Linux (RTM0RC0000XDVDC301SL41C) -# DVD Encryption Library for Linux (RTM0RC0000XDVDF301SL41C) -#DISTRO_FEATURES_append = " dvd" -#DISTRO_FEATURES_append = " dvd_encryption_library" - -# ADSP Driver for Linux (RCG3AHPDL4101ZDO) -# ADSP Interface for Linux (RCG3AHIFL4101ZDP) -# ADSP Framework (RCG3AHFWN0201ZDP) -#DISTRO_FEATURES_append = " adsp" - -# AVB Software Package for Linux -#DISTRO_FEATURES_append = " avb" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Evaluation packages -#DISTRO_FEATURES_append = " use_eva_pkg" - -# Configuration for ivi-shell and ivi-extension -#DISTRO_FEATURES_append = " ivi-shell" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/bsp/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/bsp/bblayers.conf deleted file mode 100644 index 3b2c068a..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/bsp/bblayers.conf +++ /dev/null @@ -1,15 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - ${TOPDIR}/../meta-linaro/meta-optee \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/bsp/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/bsp/local-wayland.conf deleted file mode 100644 index 57535bd6..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/bsp/local-wayland.conf +++ /dev/null @@ -1,279 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone-yocto" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "h3ulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - -# -# Yocto Project SState Mirror -# -# The Yocto Project has prebuilt artefacts available for its releases, you can enable -# use of these by uncommenting the following line. This will mean the build uses -# the network to check for artefacts at the start of builds, which does slow it down -# equally, it will also speed up the builds by not having to build things if they are -# present in the cache. It assumes you can download something faster than you can build it -# which will depend on your network. -# -#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH" - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl2-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl2-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl2-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# for Wayland/Weston weston-laucher -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" - -# Mask the wayland related to GFX -BBMASK .= "|gles-user-module|kernel-module-gles|wayland-kms|libgbm" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Mask the gstreamer recipe for MMP -BBMASK .= "|meta-renesas/meta-rcar-gen3/recipes-multimedia/gstreamer" - -# Add for gstreamer plugins ugly -LICENSE_FLAGS_WHITELIST = "commercial" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/bsp/local.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/bsp/local.conf deleted file mode 100644 index 3eb69269..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/bsp/local.conf +++ /dev/null @@ -1,272 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone-yocto" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "h3ulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - -# -# Yocto Project SState Mirror -# -# The Yocto Project has prebuilt artefacts available for its releases, you can enable -# use of these by uncommenting the following line. This will mean the build uses -# the network to check for artefacts at the start of builds, which does slow it down -# equally, it will also speed up the builds by not having to build things if they are -# present in the cache. It assumes you can download something faster than you can build it -# which will depend on your network. -# -#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH" - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl2-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl2-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl2-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Mask graphic Pkgs -BBMASK .= "|gles-user-module|kernel-module-gles|wayland-kms|libgbm" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Enable pam distro feature -DISTRO_FEATURES_append = " pam" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/gfx-only/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/gfx-only/bblayers.conf deleted file mode 100644 index 882db523..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/gfx-only/bblayers.conf +++ /dev/null @@ -1,15 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/gfx-only/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/gfx-only/local-wayland.conf deleted file mode 100644 index 683ae4ec..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/gfx-only/local-wayland.conf +++ /dev/null @@ -1,285 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone-yocto" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "h3ulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - -# -# Yocto Project SState Mirror -# -# The Yocto Project has prebuilt artefacts available for its releases, you can enable -# use of these by uncommenting the following line. This will mean the build uses -# the network to check for artefacts at the start of builds, which does slow it down -# equally, it will also speed up the builds by not having to build things if they are -# present in the cache. It assumes you can download something faster than you can build it -# which will depend on your network. -# -#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH" - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl2-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl2-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl2-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Enable Gfx Pkgs -MACHINE_FEATURES_append = " gsx" -MULTI_PROVIDER_WHITELIST += "virtual/libgl virtual/egl virtual/libgles1 virtual/libgles2" - -# for Wayland/Weston -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" -PREFERRED_PROVIDER_virtual/libgles1 = "" -PREFERRED_PROVIDER_virtual/libgles2 = "gles-user-module" -PREFERRED_PROVIDER_virtual/egl = "libegl" -PREFERRED_PROVIDER_virtual/libgl = "" -PREFERRED_PROVIDER_virtual/mesa = "" -PREFERRED_PROVIDER_virtual/libgbm = "libgbm" -PREFERRED_PROVIDER_libgbm-dev = "libgbm" -BBMASK .= "|mesa-gl" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Add for gstreamer plugins ugly -LICENSE_FLAGS_WHITELIST = "commercial" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/mmp/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/mmp/bblayers.conf deleted file mode 100644 index 882db523..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/mmp/bblayers.conf +++ /dev/null @@ -1,15 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/mmp/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/mmp/local-wayland.conf deleted file mode 100644 index 9b2cb09d..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/mmp/local-wayland.conf +++ /dev/null @@ -1,391 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone-yocto" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "h3ulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - -# -# Yocto Project SState Mirror -# -# The Yocto Project has prebuilt artefacts available for its releases, you can enable -# use of these by uncommenting the following line. This will mean the build uses -# the network to check for artefacts at the start of builds, which does slow it down -# equally, it will also speed up the builds by not having to build things if they are -# present in the cache. It assumes you can download something faster than you can build it -# which will depend on your network. -# -#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH" - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl2-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl2-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl2-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Enable Gfx Pkgs -MACHINE_FEATURES_append = " gsx" -MULTI_PROVIDER_WHITELIST += "virtual/libgl virtual/egl virtual/libgles1 virtual/libgles2" - -# for Wayland/Weston -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" -PREFERRED_PROVIDER_virtual/libgles1 = "" -PREFERRED_PROVIDER_virtual/libgles2 = "gles-user-module" -PREFERRED_PROVIDER_virtual/egl = "libegl" -PREFERRED_PROVIDER_virtual/libgl = "" -PREFERRED_PROVIDER_virtual/mesa = "" -PREFERRED_PROVIDER_virtual/libgbm = "libgbm" -PREFERRED_PROVIDER_libgbm-dev = "libgbm" -BBMASK .= "|mesa-gl" - -# Enable Multimedia features -MACHINE_FEATURES_append = " multimedia" - -# for gstreamer omx plugins -LICENSE_FLAGS_WHITELIST = "commercial" -# for mmp test program -DISTRO_FEATURES_append = " mm-test" - -# for weston v4l2 renderer -#DISTRO_FEATURES_append = " v4l2-renderer" - -# OMX H263 decoder library for Linux (RTM0AC0000XV263D30SL41C) -#DISTRO_FEATURES_append = " h263dec_lib" - -# OMX H264 decoder library for Linux (RTM0AC0000XV264D30SL41C) -DISTRO_FEATURES_append = " h264dec_lib" - -# OMX H264 encoder library for Linux (RTM0AC0000XV264E30SL41C) -#DISTRO_FEATURES_append = " h264enc_lib" - -# OMX H265 decoder library for Linux (RTM0AC0000XV265D30SL41C) -#DISTRO_FEATURES_append = " h265dec_lib" - -# OMX MPEG2 decoder library for Linux (RTM0AC0000XVM2VD30SL41C) -#DISTRO_FEATURES_append = " mpeg2dec_lib" - -# OMX Media Component MPEG4 Decoder Library for Linux (RTM0AC0000XVM4VD30SL41C) -#DISTRO_FEATURES_append = " mpeg4dec_lib" - -# OMX Media Component VC-1 Decoder Library for Linux (RTM0AC0000XVVC1D30SL41C) -#DISTRO_FEATURES_append = " vc1dec_lib" - -# OMX Media Component DivXD Decoder Library for Linux (RTM0AC0000XVDVXD30SL41C) -#DISTRO_FEATURES_append = " divxdec_lib" - -# OMX Media Component RealVideo Decoder Library for Linux (RTM0AC0000XVRLVD30SL41C) -#DISTRO_FEATURES_append = " rvdec_lib" - -# OMX Media Component ALAC Decoder Library for Linux (RTM0AC0000XAALAD30SL41C) -#DISTRO_FEATURES_append = " alacdec_lib" - -# OMX Media Component FLAC Decoder Library for Linux (RTM0AC0000XAFLAD30SL41C) -#DISTRO_FEATURES_append = " flacdec_lib" - -# OMX AAC-LC decoder library for Linux (RTM0AC0000XAAACD30SL41C), -# AAC-LC 2ch decoder middleware library for Linux (RTM0AC0000ADAACMZ1SL41C) -DISTRO_FEATURES_append = " aaclcdec_lib" -DISTRO_FEATURES_append = " aaclcdec_mdw" - -# OMX aacPlus V2 decoder library for Linux (RTM0AC0000XAAAPD30SL41C), -# aacPlus V2 decoder middleware library for Linux (RTM0AC0000ADAAPMZ1SL41C) -#DISTRO_FEATURES_append = " aacpv2dec_lib" -#DISTRO_FEATURES_append = " aacpv2dec_mdw" - -# OMX MP3 decoder library for Linux (RTM0AC0000XAMP3D30SL41C), -# MP3 decoder middleware library for Linux (RTM0AC0000ADMP3MZ1SL41C) -#DISTRO_FEATURES_append = " mp3dec_lib" -#DISTRO_FEATURES_append = " mp3dec_mdw" - -# OMX WMA decoder library for Linux (RTM0AC0000XAWMAD30SL41C), -# WMA decoder middleware library for Linux (RTM0AC0000ADWMAMZ1SL41C) -#DISTRO_FEATURES_append = " wmadec_lib" -#DISTRO_FEATURES_append = " wmadec_mdw" - -# OMX AAC-LC encoder library for Linux (RTM0AC0000XAAACE30SL41C) -# AAC-LC encoder middleware library for Linux (RTM0AC0000AEAACMZ1SL41C) -#DISTRO_FEATURES_append = " aaclcenc_lib" -#DISTRO_FEATURES_append = " aaclcenc_mdw" - -# OMX Dolby(R) Digital decoder library for Linux (RTM0AC0000XADD5D30SL41C), -# Dolby(R) Digital decoder middleware library for Linux (RTM0AC0000ADDD5MZ1SL41C) -#DISTRO_FEATURES_append = " dddec_lib" -#DISTRO_FEATURES_append = " dddec_mdw" - -# OMX Media Component VP8 Decoder Library for Linux (RTM0AC0000XVVP8D30SL41C) -#DISTRO_FEATURES_append = " vp8dec_lib" - -# OMX Media Component VP8 Encoder Library for Linux (RTM0AC0000XVVP8E30SL41C) -#DISTRO_FEATURES_append = " vp8enc_lib" - -# CMS Basic Color Management Middleware for Linux (RTM0AC0000JRCMBCV0SL41C) -#DISTRO_FEATURES_append = " cmsbcm" - -# CMS CMM3 Backlight Control Middleware for Linux (RTM0AC0000JRCMBLC0SL41C) -#DISTRO_FEATURES_append = " cmsblc" - -# CMS VSP2 Dynamic Gamma Correction Middleware for Linux (RTM0AC0000JRCMDGV0SL41C) -#DISTRO_FEATURES_append = " cmsdgc" - -# ISDB-T DTV Software Package for Linux (RTM0RC0000TE020000SL41C) -#DISTRO_FEATURES_append = " dtv" - -# DVD Core-Middleware for Linux (RTM0RC0000XDVDC301SL41C) -# DVD Encryption Library for Linux (RTM0RC0000XDVDF301SL41C) -#DISTRO_FEATURES_append = " dvd" -#DISTRO_FEATURES_append = " dvd_encryption_library" - -# ADSP Driver for Linux (RCG3AHPDL4101ZDO) -# ADSP Interface for Linux (RCG3AHIFL4101ZDP) -# ADSP Framework (RCG3AHFWN0201ZDP) -#DISTRO_FEATURES_append = " adsp" - -# AVB Software Package for Linux -#DISTRO_FEATURES_append = " avb" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Evaluation packages -#DISTRO_FEATURES_append = " use_eva_pkg" - -# Configuration for ivi-shell and ivi-extension -#DISTRO_FEATURES_append = " ivi-shell" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/linaro-gcc/bsp/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/linaro-gcc/bsp/bblayers.conf deleted file mode 100644 index 96ff8ada..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/linaro-gcc/bsp/bblayers.conf +++ /dev/null @@ -1,16 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-linaro-toolchain \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/linaro-gcc/bsp/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/linaro-gcc/bsp/local-wayland.conf deleted file mode 100644 index 7e71ed0c..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/linaro-gcc/bsp/local-wayland.conf +++ /dev/null @@ -1,268 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "m3nulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# Linaro GCC -GCCVERSION = "linaro-7.2" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# for Wayland/Weston weston-laucher -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" - -# Mask the wayland related to GFX -BBMASK .= "|gles-user-module|kernel-module-gles|wayland-kms|libgbm" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Mask the gstreamer recipe for MMP -BBMASK .= "|meta-renesas/meta-rcar-gen3/recipes-multimedia/gstreamer" - -# Add for gstreamer plugins ugly -LICENSE_FLAGS_WHITELIST = "commercial" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/linaro-gcc/bsp/local.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/linaro-gcc/bsp/local.conf deleted file mode 100644 index 087a3a3e..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/linaro-gcc/bsp/local.conf +++ /dev/null @@ -1,261 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "m3nulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# Linaro GCC -GCCVERSION = "linaro-7.2" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Mask graphic Pkgs -BBMASK .= "|gles-user-module|kernel-module-gles|wayland-kms|libgbm" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Enable pam distro feature -DISTRO_FEATURES_append = " pam" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/linaro-gcc/gfx-only/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/linaro-gcc/gfx-only/bblayers.conf deleted file mode 100644 index 96ff8ada..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/linaro-gcc/gfx-only/bblayers.conf +++ /dev/null @@ -1,16 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-linaro-toolchain \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/linaro-gcc/gfx-only/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/linaro-gcc/gfx-only/local-wayland.conf deleted file mode 100644 index 204a5043..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/linaro-gcc/gfx-only/local-wayland.conf +++ /dev/null @@ -1,274 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "m3nulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# Linaro GCC -GCCVERSION = "linaro-7.2" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Enable Gfx Pkgs -MACHINE_FEATURES_append = " gsx" -MULTI_PROVIDER_WHITELIST += "virtual/libgl virtual/egl virtual/libgles1 virtual/libgles2" - -# for Wayland/Weston -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" -PREFERRED_PROVIDER_virtual/libgles1 = "" -PREFERRED_PROVIDER_virtual/libgles2 = "gles-user-module" -PREFERRED_PROVIDER_virtual/egl = "libegl" -PREFERRED_PROVIDER_virtual/libgl = "" -PREFERRED_PROVIDER_virtual/mesa = "" -PREFERRED_PROVIDER_libgbm = "libgbm" -PREFERRED_PROVIDER_libgbm-dev = "libgbm" -BBMASK .= "|mesa-gl" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Add for gstreamer plugins ugly -LICENSE_FLAGS_WHITELIST = "commercial" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/linaro-gcc/mmp/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/linaro-gcc/mmp/bblayers.conf deleted file mode 100644 index 96ff8ada..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/linaro-gcc/mmp/bblayers.conf +++ /dev/null @@ -1,16 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-linaro-toolchain \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/linaro-gcc/mmp/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/linaro-gcc/mmp/local-wayland.conf deleted file mode 100644 index b0eedb19..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/linaro-gcc/mmp/local-wayland.conf +++ /dev/null @@ -1,380 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "m3nulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# Linaro GCC -GCCVERSION = "linaro-7.2" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Enable Gfx Pkgs -MACHINE_FEATURES_append = " gsx" -MULTI_PROVIDER_WHITELIST += "virtual/libgl virtual/egl virtual/libgles1 virtual/libgles2" - -# for Wayland/Weston -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" -PREFERRED_PROVIDER_virtual/libgles1 = "" -PREFERRED_PROVIDER_virtual/libgles2 = "gles-user-module" -PREFERRED_PROVIDER_virtual/egl = "libegl" -PREFERRED_PROVIDER_virtual/libgl = "" -PREFERRED_PROVIDER_virtual/mesa = "" -PREFERRED_PROVIDER_libgbm = "libgbm" -PREFERRED_PROVIDER_libgbm-dev = "libgbm" -BBMASK .= "|mesa-gl" - -# Enable Multimedia features -MACHINE_FEATURES_append = " multimedia" - -# for gstreamer omx plugins -LICENSE_FLAGS_WHITELIST = "commercial" -# for mmp test program -DISTRO_FEATURES_append = " mm-test" - -# for weston v4l2 renderer -#DISTRO_FEATURES_append = " v4l2-renderer" - -# OMX H263 decoder library for Linux (RTM0AC0000XV263D30SL41C) -#DISTRO_FEATURES_append = " h263dec_lib" - -# OMX H264 decoder library for Linux (RTM0AC0000XV264D30SL41C) -DISTRO_FEATURES_append = " h264dec_lib" - -# OMX H264 encoder library for Linux (RTM0AC0000XV264E30SL41C) -#DISTRO_FEATURES_append = " h264enc_lib" - -# OMX H265 decoder library for Linux (RTM0AC0000XV265D30SL41C) -#DISTRO_FEATURES_append = " h265dec_lib" - -# OMX MPEG2 decoder library for Linux (RTM0AC0000XVM2VD30SL41C) -#DISTRO_FEATURES_append = " mpeg2dec_lib" - -# OMX Media Component MPEG4 Decoder Library for Linux (RTM0AC0000XVM4VD30SL41C) -#DISTRO_FEATURES_append = " mpeg4dec_lib" - -# OMX Media Component VC-1 Decoder Library for Linux (RTM0AC0000XVVC1D30SL41C) -#DISTRO_FEATURES_append = " vc1dec_lib" - -# OMX Media Component DivXD Decoder Library for Linux (RTM0AC0000XVDVXD30SL41C) -#DISTRO_FEATURES_append = " divxdec_lib" - -# OMX Media Component RealVideo Decoder Library for Linux (RTM0AC0000XVRLVD30SL41C) -#DISTRO_FEATURES_append = " rvdec_lib" - -# OMX Media Component ALAC Decoder Library for Linux (RTM0AC0000XAALAD30SL41C) -#DISTRO_FEATURES_append = " alacdec_lib" - -# OMX Media Component FLAC Decoder Library for Linux (RTM0AC0000XAFLAD30SL41C) -#DISTRO_FEATURES_append = " flacdec_lib" - -# OMX AAC-LC decoder library for Linux (RTM0AC0000XAAACD30SL41C), -# AAC-LC 2ch decoder middleware library for Linux (RTM0AC0000ADAACMZ1SL41C) -DISTRO_FEATURES_append = " aaclcdec_lib" -DISTRO_FEATURES_append = " aaclcdec_mdw" - -# OMX aacPlus V2 decoder library for Linux (RTM0AC0000XAAAPD30SL41C), -# aacPlus V2 decoder middleware library for Linux (RTM0AC0000ADAAPMZ1SL41C) -#DISTRO_FEATURES_append = " aacpv2dec_lib" -#DISTRO_FEATURES_append = " aacpv2dec_mdw" - -# OMX MP3 decoder library for Linux (RTM0AC0000XAMP3D30SL41C), -# MP3 decoder middleware library for Linux (RTM0AC0000ADMP3MZ1SL41C) -#DISTRO_FEATURES_append = " mp3dec_lib" -#DISTRO_FEATURES_append = " mp3dec_mdw" - -# OMX WMA decoder library for Linux (RTM0AC0000XAWMAD30SL41C), -# WMA decoder middleware library for Linux (RTM0AC0000ADWMAMZ1SL41C) -#DISTRO_FEATURES_append = " wmadec_lib" -#DISTRO_FEATURES_append = " wmadec_mdw" - -# OMX AAC-LC encoder library for Linux (RTM0AC0000XAAACE30SL41C) -# AAC-LC encoder middleware library for Linux (RTM0AC0000AEAACMZ1SL41C) -#DISTRO_FEATURES_append = " aaclcenc_lib" -#DISTRO_FEATURES_append = " aaclcenc_mdw" - -# OMX Dolby(R) Digital decoder library for Linux (RTM0AC0000XADD5D30SL41C), -# Dolby(R) Digital decoder middleware library for Linux (RTM0AC0000ADDD5MZ1SL41C) -#DISTRO_FEATURES_append = " dddec_lib" -#DISTRO_FEATURES_append = " dddec_mdw" - -# OMX Media Component VP8 Decoder Library for Linux (RTM0AC0000XVVP8D30SL41C) -#DISTRO_FEATURES_append = " vp8dec_lib" - -# OMX Media Component VP8 Encoder Library for Linux (RTM0AC0000XVVP8E30SL41C) -#DISTRO_FEATURES_append = " vp8enc_lib" - -# OMX Media Component VP9 Decoder Library for Linux (RTM0AC0000XVVP9D30SL41C) -#DISTRO_FEATURES_append = " vp9dec_lib" - -# CMS Basic Color Management Middleware for Linux (RTM0AC0000JRCMBCV0SL41C) -#DISTRO_FEATURES_append = " cmsbcm" - -# CMS CMM3 Backlight Control Middleware for Linux (RTM0AC0000JRCMBLC0SL41C) -#DISTRO_FEATURES_append = " cmsblc" - -# CMS VSP2 Dynamic Gamma Correction Middleware for Linux (RTM0AC0000JRCMDGV0SL41C) -#DISTRO_FEATURES_append = " cmsdgc" - -# ISDB-T DTV Software Package for Linux (RTM0RC0000TE020000SL41C) -#DISTRO_FEATURES_append = " dtv" - -# DVD Core-Middleware for Linux (RTM0RC0000XDVDC301SL41C) -# DVD Encryption Library for Linux (RTM0RC0000XDVDF301SL41C) -#DISTRO_FEATURES_append = " dvd" -#DISTRO_FEATURES_append = " dvd_encryption_library" - -# ADSP Driver for Linux (RCG3AHPDL4101ZDO) -# ADSP Interface for Linux (RCG3AHIFL4101ZDP) -# ADSP Framework (RCG3AHFWN0201ZDP) -#DISTRO_FEATURES_append = " adsp" - -# AVB Software Package for Linux -#DISTRO_FEATURES_append = " avb" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Configuration for ivi-shell and ivi-extension -#DISTRO_FEATURES_append = " ivi-shell" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/poky-gcc/bsp/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/poky-gcc/bsp/bblayers.conf deleted file mode 100644 index 3b2c068a..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/poky-gcc/bsp/bblayers.conf +++ /dev/null @@ -1,15 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - ${TOPDIR}/../meta-linaro/meta-optee \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/poky-gcc/bsp/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/poky-gcc/bsp/local-wayland.conf deleted file mode 100644 index 0a4a79be..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/poky-gcc/bsp/local-wayland.conf +++ /dev/null @@ -1,265 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "m3nulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# for Wayland/Weston weston-laucher -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" - -# Mask the wayland related to GFX -BBMASK .= "|gles-user-module|kernel-module-gles|wayland-kms|libgbm" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Mask the gstreamer recipe for MMP -BBMASK .= "|meta-renesas/meta-rcar-gen3/recipes-multimedia/gstreamer" - -# Add for gstreamer plugins ugly -LICENSE_FLAGS_WHITELIST = "commercial" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/poky-gcc/bsp/local.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/poky-gcc/bsp/local.conf deleted file mode 100644 index 4114bd5d..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/poky-gcc/bsp/local.conf +++ /dev/null @@ -1,258 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "m3nulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Mask graphic Pkgs -BBMASK .= "|gles-user-module|kernel-module-gles|wayland-kms|libgbm" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Enable pam distro feature -DISTRO_FEATURES_append = " pam" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/poky-gcc/gfx-only/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/poky-gcc/gfx-only/bblayers.conf deleted file mode 100644 index 882db523..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/poky-gcc/gfx-only/bblayers.conf +++ /dev/null @@ -1,15 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/poky-gcc/gfx-only/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/poky-gcc/gfx-only/local-wayland.conf deleted file mode 100644 index 77d6778d..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/poky-gcc/gfx-only/local-wayland.conf +++ /dev/null @@ -1,271 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "m3nulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Enable Gfx Pkgs -MACHINE_FEATURES_append = " gsx" -MULTI_PROVIDER_WHITELIST += "virtual/libgl virtual/egl virtual/libgles1 virtual/libgles2" - -# for Wayland/Weston -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" -PREFERRED_PROVIDER_virtual/libgles1 = "" -PREFERRED_PROVIDER_virtual/libgles2 = "gles-user-module" -PREFERRED_PROVIDER_virtual/egl = "libegl" -PREFERRED_PROVIDER_virtual/libgl = "" -PREFERRED_PROVIDER_virtual/mesa = "" -PREFERRED_PROVIDER_libgbm = "libgbm" -PREFERRED_PROVIDER_libgbm-dev = "libgbm" -BBMASK .= "|mesa-gl" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Add for gstreamer plugins ugly -LICENSE_FLAGS_WHITELIST = "commercial" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/poky-gcc/mmp/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/poky-gcc/mmp/bblayers.conf deleted file mode 100644 index 882db523..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/poky-gcc/mmp/bblayers.conf +++ /dev/null @@ -1,15 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/poky-gcc/mmp/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/poky-gcc/mmp/local-wayland.conf deleted file mode 100644 index a73b537b..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3nulcb/poky-gcc/mmp/local-wayland.conf +++ /dev/null @@ -1,377 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "m3nulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Enable Gfx Pkgs -MACHINE_FEATURES_append = " gsx" -MULTI_PROVIDER_WHITELIST += "virtual/libgl virtual/egl virtual/libgles1 virtual/libgles2" - -# for Wayland/Weston -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" -PREFERRED_PROVIDER_virtual/libgles1 = "" -PREFERRED_PROVIDER_virtual/libgles2 = "gles-user-module" -PREFERRED_PROVIDER_virtual/egl = "libegl" -PREFERRED_PROVIDER_virtual/libgl = "" -PREFERRED_PROVIDER_virtual/mesa = "" -PREFERRED_PROVIDER_libgbm = "libgbm" -PREFERRED_PROVIDER_libgbm-dev = "libgbm" -BBMASK .= "|mesa-gl" - -# Enable Multimedia features -MACHINE_FEATURES_append = " multimedia" - -# for gstreamer omx plugins -LICENSE_FLAGS_WHITELIST = "commercial" -# for mmp test program -DISTRO_FEATURES_append = " mm-test" - -# for weston v4l2 renderer -#DISTRO_FEATURES_append = " v4l2-renderer" - -# OMX H263 decoder library for Linux (RTM0AC0000XV263D30SL41C) -#DISTRO_FEATURES_append = " h263dec_lib" - -# OMX H264 decoder library for Linux (RTM0AC0000XV264D30SL41C) -DISTRO_FEATURES_append = " h264dec_lib" - -# OMX H264 encoder library for Linux (RTM0AC0000XV264E30SL41C) -#DISTRO_FEATURES_append = " h264enc_lib" - -# OMX H265 decoder library for Linux (RTM0AC0000XV265D30SL41C) -#DISTRO_FEATURES_append = " h265dec_lib" - -# OMX MPEG2 decoder library for Linux (RTM0AC0000XVM2VD30SL41C) -#DISTRO_FEATURES_append = " mpeg2dec_lib" - -# OMX Media Component MPEG4 Decoder Library for Linux (RTM0AC0000XVM4VD30SL41C) -#DISTRO_FEATURES_append = " mpeg4dec_lib" - -# OMX Media Component VC-1 Decoder Library for Linux (RTM0AC0000XVVC1D30SL41C) -#DISTRO_FEATURES_append = " vc1dec_lib" - -# OMX Media Component DivXD Decoder Library for Linux (RTM0AC0000XVDVXD30SL41C) -#DISTRO_FEATURES_append = " divxdec_lib" - -# OMX Media Component RealVideo Decoder Library for Linux (RTM0AC0000XVRLVD30SL41C) -#DISTRO_FEATURES_append = " rvdec_lib" - -# OMX Media Component ALAC Decoder Library for Linux (RTM0AC0000XAALAD30SL41C) -#DISTRO_FEATURES_append = " alacdec_lib" - -# OMX Media Component FLAC Decoder Library for Linux (RTM0AC0000XAFLAD30SL41C) -#DISTRO_FEATURES_append = " flacdec_lib" - -# OMX AAC-LC decoder library for Linux (RTM0AC0000XAAACD30SL41C), -# AAC-LC 2ch decoder middleware library for Linux (RTM0AC0000ADAACMZ1SL41C) -DISTRO_FEATURES_append = " aaclcdec_lib" -DISTRO_FEATURES_append = " aaclcdec_mdw" - -# OMX aacPlus V2 decoder library for Linux (RTM0AC0000XAAAPD30SL41C), -# aacPlus V2 decoder middleware library for Linux (RTM0AC0000ADAAPMZ1SL41C) -#DISTRO_FEATURES_append = " aacpv2dec_lib" -#DISTRO_FEATURES_append = " aacpv2dec_mdw" - -# OMX MP3 decoder library for Linux (RTM0AC0000XAMP3D30SL41C), -# MP3 decoder middleware library for Linux (RTM0AC0000ADMP3MZ1SL41C) -#DISTRO_FEATURES_append = " mp3dec_lib" -#DISTRO_FEATURES_append = " mp3dec_mdw" - -# OMX WMA decoder library for Linux (RTM0AC0000XAWMAD30SL41C), -# WMA decoder middleware library for Linux (RTM0AC0000ADWMAMZ1SL41C) -#DISTRO_FEATURES_append = " wmadec_lib" -#DISTRO_FEATURES_append = " wmadec_mdw" - -# OMX AAC-LC encoder library for Linux (RTM0AC0000XAAACE30SL41C) -# AAC-LC encoder middleware library for Linux (RTM0AC0000AEAACMZ1SL41C) -#DISTRO_FEATURES_append = " aaclcenc_lib" -#DISTRO_FEATURES_append = " aaclcenc_mdw" - -# OMX Dolby(R) Digital decoder library for Linux (RTM0AC0000XADD5D30SL41C), -# Dolby(R) Digital decoder middleware library for Linux (RTM0AC0000ADDD5MZ1SL41C) -#DISTRO_FEATURES_append = " dddec_lib" -#DISTRO_FEATURES_append = " dddec_mdw" - -# OMX Media Component VP8 Decoder Library for Linux (RTM0AC0000XVVP8D30SL41C) -#DISTRO_FEATURES_append = " vp8dec_lib" - -# OMX Media Component VP8 Encoder Library for Linux (RTM0AC0000XVVP8E30SL41C) -#DISTRO_FEATURES_append = " vp8enc_lib" - -# OMX Media Component VP9 Decoder Library for Linux (RTM0AC0000XVVP9D30SL41C) -#DISTRO_FEATURES_append = " vp9dec_lib" - -# CMS Basic Color Management Middleware for Linux (RTM0AC0000JRCMBCV0SL41C) -#DISTRO_FEATURES_append = " cmsbcm" - -# CMS CMM3 Backlight Control Middleware for Linux (RTM0AC0000JRCMBLC0SL41C) -#DISTRO_FEATURES_append = " cmsblc" - -# CMS VSP2 Dynamic Gamma Correction Middleware for Linux (RTM0AC0000JRCMDGV0SL41C) -#DISTRO_FEATURES_append = " cmsdgc" - -# ISDB-T DTV Software Package for Linux (RTM0RC0000TE020000SL41C) -#DISTRO_FEATURES_append = " dtv" - -# DVD Core-Middleware for Linux (RTM0RC0000XDVDC301SL41C) -# DVD Encryption Library for Linux (RTM0RC0000XDVDF301SL41C) -#DISTRO_FEATURES_append = " dvd" -#DISTRO_FEATURES_append = " dvd_encryption_library" - -# ADSP Driver for Linux (RCG3AHPDL4101ZDO) -# ADSP Interface for Linux (RCG3AHIFL4101ZDP) -# ADSP Framework (RCG3AHFWN0201ZDP) -#DISTRO_FEATURES_append = " adsp" - -# AVB Software Package for Linux -#DISTRO_FEATURES_append = " avb" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Configuration for ivi-shell and ivi-extension -#DISTRO_FEATURES_append = " ivi-shell" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/bsp/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/bsp/bblayers.conf deleted file mode 100644 index 96ff8ada..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/bsp/bblayers.conf +++ /dev/null @@ -1,16 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-linaro-toolchain \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/bsp/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/bsp/local-wayland.conf deleted file mode 100644 index 0b6f13c4..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/bsp/local-wayland.conf +++ /dev/null @@ -1,271 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "m3ulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# Linaro GCC -GCCVERSION = "linaro-7.2" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# for Wayland/Weston weston-laucher -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" - -# Mask the wayland related to GFX -BBMASK .= "|gles-user-module|kernel-module-gles|wayland-kms|libgbm" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Mask the gstreamer recipe for MMP -BBMASK .= "|meta-renesas/meta-rcar-gen3/recipes-multimedia/gstreamer" - -# Add for gstreamer plugins ugly -LICENSE_FLAGS_WHITELIST = "commercial" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/bsp/local.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/bsp/local.conf deleted file mode 100644 index 3c63eff8..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/bsp/local.conf +++ /dev/null @@ -1,264 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "m3ulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# Linaro GCC -GCCVERSION = "linaro-7.2" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Mask graphic Pkgs -BBMASK .= "|gles-user-module|kernel-module-gles|wayland-kms|libgbm" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Enable pam distro feature -DISTRO_FEATURES_append = " pam" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/gfx-only/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/gfx-only/bblayers.conf deleted file mode 100644 index 96ff8ada..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/gfx-only/bblayers.conf +++ /dev/null @@ -1,16 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-linaro-toolchain \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/gfx-only/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/gfx-only/local-wayland.conf deleted file mode 100644 index dba007a6..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/gfx-only/local-wayland.conf +++ /dev/null @@ -1,277 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "m3ulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# Linaro GCC -GCCVERSION = "linaro-7.2" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Enable Gfx Pkgs -MACHINE_FEATURES_append = " gsx" -MULTI_PROVIDER_WHITELIST += "virtual/libgl virtual/egl virtual/libgles1 virtual/libgles2" - -# for Wayland/Weston -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" -PREFERRED_PROVIDER_virtual/libgles1 = "" -PREFERRED_PROVIDER_virtual/libgles2 = "gles-user-module" -PREFERRED_PROVIDER_virtual/egl = "libegl" -PREFERRED_PROVIDER_virtual/libgl = "" -PREFERRED_PROVIDER_virtual/mesa = "" -PREFERRED_PROVIDER_libgbm = "libgbm" -PREFERRED_PROVIDER_libgbm-dev = "libgbm" -BBMASK .= "|mesa-gl" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Add for gstreamer plugins ugly -LICENSE_FLAGS_WHITELIST = "commercial" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/mmp/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/mmp/bblayers.conf deleted file mode 100644 index 96ff8ada..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/mmp/bblayers.conf +++ /dev/null @@ -1,16 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-linaro-toolchain \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/mmp/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/mmp/local-wayland.conf deleted file mode 100644 index a96df786..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/mmp/local-wayland.conf +++ /dev/null @@ -1,383 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "m3ulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# Linaro GCC -GCCVERSION = "linaro-7.2" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Enable Gfx Pkgs -MACHINE_FEATURES_append = " gsx" -MULTI_PROVIDER_WHITELIST += "virtual/libgl virtual/egl virtual/libgles1 virtual/libgles2" - -# for Wayland/Weston -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" -PREFERRED_PROVIDER_virtual/libgles1 = "" -PREFERRED_PROVIDER_virtual/libgles2 = "gles-user-module" -PREFERRED_PROVIDER_virtual/egl = "libegl" -PREFERRED_PROVIDER_virtual/libgl = "" -PREFERRED_PROVIDER_virtual/mesa = "" -PREFERRED_PROVIDER_libgbm = "libgbm" -PREFERRED_PROVIDER_libgbm-dev = "libgbm" -BBMASK .= "|mesa-gl" - -# Enable Multimedia features -MACHINE_FEATURES_append = " multimedia" - -# for gstreamer omx plugins -LICENSE_FLAGS_WHITELIST = "commercial" -# for mmp test program -DISTRO_FEATURES_append = " mm-test" - -# for weston v4l2 renderer -#DISTRO_FEATURES_append = " v4l2-renderer" - -# OMX H263 decoder library for Linux (RTM0AC0000XV263D30SL41C) -#DISTRO_FEATURES_append = " h263dec_lib" - -# OMX H264 decoder library for Linux (RTM0AC0000XV264D30SL41C) -DISTRO_FEATURES_append = " h264dec_lib" - -# OMX H264 encoder library for Linux (RTM0AC0000XV264E30SL41C) -#DISTRO_FEATURES_append = " h264enc_lib" - -# OMX H265 decoder library for Linux (RTM0AC0000XV265D30SL41C) -#DISTRO_FEATURES_append = " h265dec_lib" - -# OMX MPEG2 decoder library for Linux (RTM0AC0000XVM2VD30SL41C) -#DISTRO_FEATURES_append = " mpeg2dec_lib" - -# OMX Media Component MPEG4 Decoder Library for Linux (RTM0AC0000XVM4VD30SL41C) -#DISTRO_FEATURES_append = " mpeg4dec_lib" - -# OMX Media Component VC-1 Decoder Library for Linux (RTM0AC0000XVVC1D30SL41C) -#DISTRO_FEATURES_append = " vc1dec_lib" - -# OMX Media Component DivXD Decoder Library for Linux (RTM0AC0000XVDVXD30SL41C) -#DISTRO_FEATURES_append = " divxdec_lib" - -# OMX Media Component RealVideo Decoder Library for Linux (RTM0AC0000XVRLVD30SL41C) -#DISTRO_FEATURES_append = " rvdec_lib" - -# OMX Media Component ALAC Decoder Library for Linux (RTM0AC0000XAALAD30SL41C) -#DISTRO_FEATURES_append = " alacdec_lib" - -# OMX Media Component FLAC Decoder Library for Linux (RTM0AC0000XAFLAD30SL41C) -#DISTRO_FEATURES_append = " flacdec_lib" - -# OMX AAC-LC decoder library for Linux (RTM0AC0000XAAACD30SL41C), -# AAC-LC 2ch decoder middleware library for Linux (RTM0AC0000ADAACMZ1SL41C) -DISTRO_FEATURES_append = " aaclcdec_lib" -DISTRO_FEATURES_append = " aaclcdec_mdw" - -# OMX aacPlus V2 decoder library for Linux (RTM0AC0000XAAAPD30SL41C), -# aacPlus V2 decoder middleware library for Linux (RTM0AC0000ADAAPMZ1SL41C) -#DISTRO_FEATURES_append = " aacpv2dec_lib" -#DISTRO_FEATURES_append = " aacpv2dec_mdw" - -# OMX MP3 decoder library for Linux (RTM0AC0000XAMP3D30SL41C), -# MP3 decoder middleware library for Linux (RTM0AC0000ADMP3MZ1SL41C) -#DISTRO_FEATURES_append = " mp3dec_lib" -#DISTRO_FEATURES_append = " mp3dec_mdw" - -# OMX WMA decoder library for Linux (RTM0AC0000XAWMAD30SL41C), -# WMA decoder middleware library for Linux (RTM0AC0000ADWMAMZ1SL41C) -#DISTRO_FEATURES_append = " wmadec_lib" -#DISTRO_FEATURES_append = " wmadec_mdw" - -# OMX AAC-LC encoder library for Linux (RTM0AC0000XAAACE30SL41C) -# AAC-LC encoder middleware library for Linux (RTM0AC0000AEAACMZ1SL41C) -#DISTRO_FEATURES_append = " aaclcenc_lib" -#DISTRO_FEATURES_append = " aaclcenc_mdw" - -# OMX Dolby(R) Digital decoder library for Linux (RTM0AC0000XADD5D30SL41C), -# Dolby(R) Digital decoder middleware library for Linux (RTM0AC0000ADDD5MZ1SL41C) -#DISTRO_FEATURES_append = " dddec_lib" -#DISTRO_FEATURES_append = " dddec_mdw" - -# OMX Media Component VP8 Decoder Library for Linux (RTM0AC0000XVVP8D30SL41C) -#DISTRO_FEATURES_append = " vp8dec_lib" - -# OMX Media Component VP8 Encoder Library for Linux (RTM0AC0000XVVP8E30SL41C) -#DISTRO_FEATURES_append = " vp8enc_lib" - -# CMS Basic Color Management Middleware for Linux (RTM0AC0000JRCMBCV0SL41C) -#DISTRO_FEATURES_append = " cmsbcm" - -# CMS CMM3 Backlight Control Middleware for Linux (RTM0AC0000JRCMBLC0SL41C) -#DISTRO_FEATURES_append = " cmsblc" - -# CMS VSP2 Dynamic Gamma Correction Middleware for Linux (RTM0AC0000JRCMDGV0SL41C) -#DISTRO_FEATURES_append = " cmsdgc" - -# ISDB-T DTV Software Package for Linux (RTM0RC0000TE020000SL41C) -#DISTRO_FEATURES_append = " dtv" - -# DVD Core-Middleware for Linux (RTM0RC0000XDVDC301SL41C) -# DVD Encryption Library for Linux (RTM0RC0000XDVDF301SL41C) -#DISTRO_FEATURES_append = " dvd" -#DISTRO_FEATURES_append = " dvd_encryption_library" - -# ADSP Driver for Linux (RCG3AHPDL4101ZDO) -# ADSP Interface for Linux (RCG3AHIFL4101ZDP) -# ADSP Framework (RCG3AHFWN0201ZDP) -#DISTRO_FEATURES_append = " adsp" - -# AVB Software Package for Linux -#DISTRO_FEATURES_append = " avb" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Evaluation packages -#DISTRO_FEATURES_append = " use_eva_pkg" - -# Configuration for ivi-shell and ivi-extension -#DISTRO_FEATURES_append = " ivi-shell" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/poky-gcc/bsp/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/poky-gcc/bsp/bblayers.conf deleted file mode 100644 index 3b2c068a..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/poky-gcc/bsp/bblayers.conf +++ /dev/null @@ -1,15 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - ${TOPDIR}/../meta-linaro/meta-optee \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/poky-gcc/bsp/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/poky-gcc/bsp/local-wayland.conf deleted file mode 100644 index d953c74a..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/poky-gcc/bsp/local-wayland.conf +++ /dev/null @@ -1,279 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone-yocto" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "m3ulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - -# -# Yocto Project SState Mirror -# -# The Yocto Project has prebuilt artefacts available for its releases, you can enable -# use of these by uncommenting the following line. This will mean the build uses -# the network to check for artefacts at the start of builds, which does slow it down -# equally, it will also speed up the builds by not having to build things if they are -# present in the cache. It assumes you can download something faster than you can build it -# which will depend on your network. -# -#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH" - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl2-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl2-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl2-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# for Wayland/Weston weston-laucher -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" - -# Mask the wayland related to GFX -BBMASK .= "|gles-user-module|kernel-module-gles|wayland-kms|libgbm" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Mask the gstreamer recipe for MMP -BBMASK .= "|meta-renesas/meta-rcar-gen3/recipes-multimedia/gstreamer" - -# Add for gstreamer plugins ugly -LICENSE_FLAGS_WHITELIST = "commercial" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/poky-gcc/bsp/local.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/poky-gcc/bsp/local.conf deleted file mode 100644 index 672e16b8..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/poky-gcc/bsp/local.conf +++ /dev/null @@ -1,272 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone-yocto" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "m3ulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - -# -# Yocto Project SState Mirror -# -# The Yocto Project has prebuilt artefacts available for its releases, you can enable -# use of these by uncommenting the following line. This will mean the build uses -# the network to check for artefacts at the start of builds, which does slow it down -# equally, it will also speed up the builds by not having to build things if they are -# present in the cache. It assumes you can download something faster than you can build it -# which will depend on your network. -# -#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH" - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl2-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl2-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl2-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Mask graphic Pkgs -BBMASK .= "|gles-user-module|kernel-module-gles|wayland-kms|libgbm" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Enable pam distro feature -DISTRO_FEATURES_append = " pam" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/poky-gcc/gfx-only/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/poky-gcc/gfx-only/bblayers.conf deleted file mode 100644 index 882db523..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/poky-gcc/gfx-only/bblayers.conf +++ /dev/null @@ -1,15 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/poky-gcc/gfx-only/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/poky-gcc/gfx-only/local-wayland.conf deleted file mode 100644 index 7b8f40cf..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/poky-gcc/gfx-only/local-wayland.conf +++ /dev/null @@ -1,285 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone-yocto" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "m3ulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - -# -# Yocto Project SState Mirror -# -# The Yocto Project has prebuilt artefacts available for its releases, you can enable -# use of these by uncommenting the following line. This will mean the build uses -# the network to check for artefacts at the start of builds, which does slow it down -# equally, it will also speed up the builds by not having to build things if they are -# present in the cache. It assumes you can download something faster than you can build it -# which will depend on your network. -# -#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH" - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl2-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl2-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl2-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Enable Gfx Pkgs -MACHINE_FEATURES_append = " gsx" -MULTI_PROVIDER_WHITELIST += "virtual/libgl virtual/egl virtual/libgles1 virtual/libgles2" - -# for Wayland/Weston -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" -PREFERRED_PROVIDER_virtual/libgles1 = "" -PREFERRED_PROVIDER_virtual/libgles2 = "gles-user-module" -PREFERRED_PROVIDER_virtual/egl = "libegl" -PREFERRED_PROVIDER_virtual/libgl = "" -PREFERRED_PROVIDER_virtual/mesa = "" -PREFERRED_PROVIDER_virtual/libgbm = "libgbm" -PREFERRED_PROVIDER_libgbm-dev = "libgbm" -BBMASK .= "|mesa-gl" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Add for gstreamer plugins ugly -LICENSE_FLAGS_WHITELIST = "commercial" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/poky-gcc/mmp/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/poky-gcc/mmp/bblayers.conf deleted file mode 100644 index 882db523..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/poky-gcc/mmp/bblayers.conf +++ /dev/null @@ -1,15 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/poky-gcc/mmp/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/poky-gcc/mmp/local-wayland.conf deleted file mode 100644 index 3300326e..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/m3ulcb/poky-gcc/mmp/local-wayland.conf +++ /dev/null @@ -1,391 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone-yocto" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "m3ulcb" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - -# -# Yocto Project SState Mirror -# -# The Yocto Project has prebuilt artefacts available for its releases, you can enable -# use of these by uncommenting the following line. This will mean the build uses -# the network to check for artefacts at the start of builds, which does slow it down -# equally, it will also speed up the builds by not having to build things if they are -# present in the cache. It assumes you can download something faster than you can build it -# which will depend on your network. -# -#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH" - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl2-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl2-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl2-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Enable Gfx Pkgs -MACHINE_FEATURES_append = " gsx" -MULTI_PROVIDER_WHITELIST += "virtual/libgl virtual/egl virtual/libgles1 virtual/libgles2" - -# for Wayland/Weston -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" -PREFERRED_PROVIDER_virtual/libgles1 = "" -PREFERRED_PROVIDER_virtual/libgles2 = "gles-user-module" -PREFERRED_PROVIDER_virtual/egl = "libegl" -PREFERRED_PROVIDER_virtual/libgl = "" -PREFERRED_PROVIDER_virtual/mesa = "" -PREFERRED_PROVIDER_virtual/libgbm = "libgbm" -PREFERRED_PROVIDER_libgbm-dev = "libgbm" -BBMASK .= "|mesa-gl" - -# Enable Multimedia features -MACHINE_FEATURES_append = " multimedia" - -# for gstreamer omx plugins -LICENSE_FLAGS_WHITELIST = "commercial" -# for mmp test program -DISTRO_FEATURES_append = " mm-test" - -# for weston v4l2 renderer -#DISTRO_FEATURES_append = " v4l2-renderer" - -# OMX H263 decoder library for Linux (RTM0AC0000XV263D30SL41C) -#DISTRO_FEATURES_append = " h263dec_lib" - -# OMX H264 decoder library for Linux (RTM0AC0000XV264D30SL41C) -DISTRO_FEATURES_append = " h264dec_lib" - -# OMX H264 encoder library for Linux (RTM0AC0000XV264E30SL41C) -#DISTRO_FEATURES_append = " h264enc_lib" - -# OMX H265 decoder library for Linux (RTM0AC0000XV265D30SL41C) -#DISTRO_FEATURES_append = " h265dec_lib" - -# OMX MPEG2 decoder library for Linux (RTM0AC0000XVM2VD30SL41C) -#DISTRO_FEATURES_append = " mpeg2dec_lib" - -# OMX Media Component MPEG4 Decoder Library for Linux (RTM0AC0000XVM4VD30SL41C) -#DISTRO_FEATURES_append = " mpeg4dec_lib" - -# OMX Media Component VC-1 Decoder Library for Linux (RTM0AC0000XVVC1D30SL41C) -#DISTRO_FEATURES_append = " vc1dec_lib" - -# OMX Media Component DivXD Decoder Library for Linux (RTM0AC0000XVDVXD30SL41C) -#DISTRO_FEATURES_append = " divxdec_lib" - -# OMX Media Component RealVideo Decoder Library for Linux (RTM0AC0000XVRLVD30SL41C) -#DISTRO_FEATURES_append = " rvdec_lib" - -# OMX Media Component ALAC Decoder Library for Linux (RTM0AC0000XAALAD30SL41C) -#DISTRO_FEATURES_append = " alacdec_lib" - -# OMX Media Component FLAC Decoder Library for Linux (RTM0AC0000XAFLAD30SL41C) -#DISTRO_FEATURES_append = " flacdec_lib" - -# OMX AAC-LC decoder library for Linux (RTM0AC0000XAAACD30SL41C), -# AAC-LC 2ch decoder middleware library for Linux (RTM0AC0000ADAACMZ1SL41C) -DISTRO_FEATURES_append = " aaclcdec_lib" -DISTRO_FEATURES_append = " aaclcdec_mdw" - -# OMX aacPlus V2 decoder library for Linux (RTM0AC0000XAAAPD30SL41C), -# aacPlus V2 decoder middleware library for Linux (RTM0AC0000ADAAPMZ1SL41C) -#DISTRO_FEATURES_append = " aacpv2dec_lib" -#DISTRO_FEATURES_append = " aacpv2dec_mdw" - -# OMX MP3 decoder library for Linux (RTM0AC0000XAMP3D30SL41C), -# MP3 decoder middleware library for Linux (RTM0AC0000ADMP3MZ1SL41C) -#DISTRO_FEATURES_append = " mp3dec_lib" -#DISTRO_FEATURES_append = " mp3dec_mdw" - -# OMX WMA decoder library for Linux (RTM0AC0000XAWMAD30SL41C), -# WMA decoder middleware library for Linux (RTM0AC0000ADWMAMZ1SL41C) -#DISTRO_FEATURES_append = " wmadec_lib" -#DISTRO_FEATURES_append = " wmadec_mdw" - -# OMX AAC-LC encoder library for Linux (RTM0AC0000XAAACE30SL41C) -# AAC-LC encoder middleware library for Linux (RTM0AC0000AEAACMZ1SL41C) -#DISTRO_FEATURES_append = " aaclcenc_lib" -#DISTRO_FEATURES_append = " aaclcenc_mdw" - -# OMX Dolby(R) Digital decoder library for Linux (RTM0AC0000XADD5D30SL41C), -# Dolby(R) Digital decoder middleware library for Linux (RTM0AC0000ADDD5MZ1SL41C) -#DISTRO_FEATURES_append = " dddec_lib" -#DISTRO_FEATURES_append = " dddec_mdw" - -# OMX Media Component VP8 Decoder Library for Linux (RTM0AC0000XVVP8D30SL41C) -#DISTRO_FEATURES_append = " vp8dec_lib" - -# OMX Media Component VP8 Encoder Library for Linux (RTM0AC0000XVVP8E30SL41C) -#DISTRO_FEATURES_append = " vp8enc_lib" - -# CMS Basic Color Management Middleware for Linux (RTM0AC0000JRCMBCV0SL41C) -#DISTRO_FEATURES_append = " cmsbcm" - -# CMS CMM3 Backlight Control Middleware for Linux (RTM0AC0000JRCMBLC0SL41C) -#DISTRO_FEATURES_append = " cmsblc" - -# CMS VSP2 Dynamic Gamma Correction Middleware for Linux (RTM0AC0000JRCMDGV0SL41C) -#DISTRO_FEATURES_append = " cmsdgc" - -# ISDB-T DTV Software Package for Linux (RTM0RC0000TE020000SL41C) -#DISTRO_FEATURES_append = " dtv" - -# DVD Core-Middleware for Linux (RTM0RC0000XDVDC301SL41C) -# DVD Encryption Library for Linux (RTM0RC0000XDVDF301SL41C) -#DISTRO_FEATURES_append = " dvd" -#DISTRO_FEATURES_append = " dvd_encryption_library" - -# ADSP Driver for Linux (RCG3AHPDL4101ZDO) -# ADSP Interface for Linux (RCG3AHIFL4101ZDP) -# ADSP Framework (RCG3AHFWN0201ZDP) -#DISTRO_FEATURES_append = " adsp" - -# AVB Software Package for Linux -#DISTRO_FEATURES_append = " avb" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Evaluation packages -#DISTRO_FEATURES_append = " use_eva_pkg" - -# Configuration for ivi-shell and ivi-extension -#DISTRO_FEATURES_append = " ivi-shell" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/bsp/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/bsp/bblayers.conf deleted file mode 100644 index 96ff8ada..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/bsp/bblayers.conf +++ /dev/null @@ -1,16 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-linaro-toolchain \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/bsp/local-ltp.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/bsp/local-ltp.conf deleted file mode 100644 index 9dd4d907..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/bsp/local-ltp.conf +++ /dev/null @@ -1,274 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "salvator-x" - -# This sets the SoC -# H3: r8a7795, M3: r8a7796, M3N: r8a77965 -SOC_FAMILY = "r8a7795" -#SOC_FAMILY = "r8a7796" -#SOC_FAMILY = "r8a77965" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks tools-sdk" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -GCCVERSION = "linaro-7.2" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Mask graphic Pkgs -BBMASK .= "|gles-user-module|kernel-module-gles|wayland-kms|libgbm" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Configuration for USB 3.0 -#MACHINE_FEATURES_append = " usb3" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" - -# Additional packages for LTP -DISTRO_FEATURES_append = " pam" -CORE_IMAGE_EXTRA_INSTALL_append = " ltp" -IMAGE_INSTALL_append = " binutils elfutils file quota tar bzip2 sudo shadow glibc-utils net-tools procps cdrkit kernel-modules" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/bsp/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/bsp/local-wayland.conf deleted file mode 100644 index ab2e8156..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/bsp/local-wayland.conf +++ /dev/null @@ -1,280 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "salvator-x" - -# This sets the SoC -# H3: r8a7795, M3: r8a7796, M3N: r8a77965 -SOC_FAMILY = "r8a7795" -#SOC_FAMILY = "r8a7796" -#SOC_FAMILY = "r8a77965" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# Linaro GCC -GCCVERSION = "linaro-7.2" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# for Wayland/Weston weston-laucher -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" - -# Mask the wayland related to GFX -BBMASK .= "|gles-user-module|kernel-module-gles|wayland-kms|libgbm" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Mask the gstreamer recipe for MMP -BBMASK .= "|meta-renesas/meta-rcar-gen3/recipes-multimedia/gstreamer" - -# Add for gstreamer plugins ugly -LICENSE_FLAGS_WHITELIST = "commercial" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Configuration for USB 3.0 -#MACHINE_FEATURES_append = " usb3" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/bsp/local.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/bsp/local.conf deleted file mode 100644 index 29c0f5db..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/bsp/local.conf +++ /dev/null @@ -1,273 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "salvator-x" - -# This sets the SoC -# H3: r8a7795, M3: r8a7796, M3N: r8a77965 -SOC_FAMILY = "r8a7795" -#SOC_FAMILY = "r8a7796" -#SOC_FAMILY = "r8a77965" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# Linaro GCC -GCCVERSION = "linaro-7.2" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Mask graphic Pkgs -BBMASK .= "|gles-user-module|kernel-module-gles|wayland-kms|libgbm" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Enable pam distro feature -DISTRO_FEATURES_append = " pam" - -# Configuration for USB 3.0 -#MACHINE_FEATURES_append = " usb3" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/gfx-only/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/gfx-only/bblayers.conf deleted file mode 100644 index 96ff8ada..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/gfx-only/bblayers.conf +++ /dev/null @@ -1,16 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-linaro-toolchain \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/gfx-only/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/gfx-only/local-wayland.conf deleted file mode 100644 index 3d798264..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/gfx-only/local-wayland.conf +++ /dev/null @@ -1,286 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "salvator-x" - -# This sets the SoC -# H3: r8a7795, M3: r8a7796, M3N: r8a77965 -SOC_FAMILY = "r8a7795" -#SOC_FAMILY = "r8a7796" -#SOC_FAMILY = "r8a77965" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# Linaro GCC -GCCVERSION = "linaro-7.2" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Enable Gfx Pkgs -MACHINE_FEATURES_append = " gsx" -MULTI_PROVIDER_WHITELIST += "virtual/libgl virtual/egl virtual/libgles1 virtual/libgles2" - -# for Wayland/Weston -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" -PREFERRED_PROVIDER_virtual/libgles1 = "" -PREFERRED_PROVIDER_virtual/libgles2 = "gles-user-module" -PREFERRED_PROVIDER_virtual/egl = "libegl" -PREFERRED_PROVIDER_virtual/libgl = "" -PREFERRED_PROVIDER_virtual/mesa = "" -PREFERRED_PROVIDER_libgbm = "libgbm" -PREFERRED_PROVIDER_libgbm-dev = "libgbm" -BBMASK .= "|mesa-gl" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Add for gstreamer plugins ugly -LICENSE_FLAGS_WHITELIST = "commercial" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Configuration for USB 3.0 -#MACHINE_FEATURES_append = " usb3" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/mmp/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/mmp/bblayers.conf deleted file mode 100644 index 96ff8ada..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/mmp/bblayers.conf +++ /dev/null @@ -1,16 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-linaro-toolchain \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/mmp/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/mmp/local-wayland.conf deleted file mode 100644 index 085d9119..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/linaro-gcc/mmp/local-wayland.conf +++ /dev/null @@ -1,395 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "salvator-x" - -# This sets the SoC -# H3: r8a7795, M3: r8a7796, M3N: r8a77965 -SOC_FAMILY = "r8a7795" -#SOC_FAMILY = "r8a7796" -#SOC_FAMILY = "r8a77965" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# Linaro GCC -GCCVERSION = "linaro-7.2" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Enable Gfx Pkgs -MACHINE_FEATURES_append = " gsx" -MULTI_PROVIDER_WHITELIST += "virtual/libgl virtual/egl virtual/libgles1 virtual/libgles2" - -# for Wayland/Weston -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" -PREFERRED_PROVIDER_virtual/libgles1 = "" -PREFERRED_PROVIDER_virtual/libgles2 = "gles-user-module" -PREFERRED_PROVIDER_virtual/egl = "libegl" -PREFERRED_PROVIDER_virtual/libgl = "" -PREFERRED_PROVIDER_virtual/mesa = "" -PREFERRED_PROVIDER_libgbm = "libgbm" -PREFERRED_PROVIDER_libgbm-dev = "libgbm" -BBMASK .= "|mesa-gl" - -# Enable Multimedia features -MACHINE_FEATURES_append = " multimedia" - -# for gstreamer omx plugins -LICENSE_FLAGS_WHITELIST = "commercial" -# for mmp test program -DISTRO_FEATURES_append = " mm-test" - -# for weston v4l2 renderer -#DISTRO_FEATURES_append = " v4l2-renderer" - -# OMX H263 decoder library for Linux (RTM0AC0000XV263D30SL41C) -#DISTRO_FEATURES_append = " h263dec_lib" - -# OMX H264 decoder library for Linux (RTM0AC0000XV264D30SL41C) -DISTRO_FEATURES_append = " h264dec_lib" - -# OMX H264 encoder library for Linux (RTM0AC0000XV264E30SL41C) -#DISTRO_FEATURES_append = " h264enc_lib" - -# OMX H265 decoder library for Linux (RTM0AC0000XV265D30SL41C) -#DISTRO_FEATURES_append = " h265dec_lib" - -# OMX MPEG2 decoder library for Linux (RTM0AC0000XVM2VD30SL41C) -#DISTRO_FEATURES_append = " mpeg2dec_lib" - -# OMX Media Component MPEG4 Decoder Library for Linux (RTM0AC0000XVM4VD30SL41C) -#DISTRO_FEATURES_append = " mpeg4dec_lib" - -# OMX Media Component VC-1 Decoder Library for Linux (RTM0AC0000XVVC1D30SL41C) -#DISTRO_FEATURES_append = " vc1dec_lib" - -# OMX Media Component DivXD Decoder Library for Linux (RTM0AC0000XVDVXD30SL41C) -#DISTRO_FEATURES_append = " divxdec_lib" - -# OMX Media Component RealVideo Decoder Library for Linux (RTM0AC0000XVRLVD30SL41C) -#DISTRO_FEATURES_append = " rvdec_lib" - -# OMX Media Component ALAC Decoder Library for Linux (RTM0AC0000XAALAD30SL41C) -#DISTRO_FEATURES_append = " alacdec_lib" - -# OMX Media Component FLAC Decoder Library for Linux (RTM0AC0000XAFLAD30SL41C) -#DISTRO_FEATURES_append = " flacdec_lib" - -# OMX AAC-LC decoder library for Linux (RTM0AC0000XAAACD30SL41C), -# AAC-LC 2ch decoder middleware library for Linux (RTM0AC0000ADAACMZ1SL41C) -DISTRO_FEATURES_append = " aaclcdec_lib" -DISTRO_FEATURES_append = " aaclcdec_mdw" - -# OMX aacPlus V2 decoder library for Linux (RTM0AC0000XAAAPD30SL41C), -# aacPlus V2 decoder middleware library for Linux (RTM0AC0000ADAAPMZ1SL41C) -#DISTRO_FEATURES_append = " aacpv2dec_lib" -#DISTRO_FEATURES_append = " aacpv2dec_mdw" - -# OMX MP3 decoder library for Linux (RTM0AC0000XAMP3D30SL41C), -# MP3 decoder middleware library for Linux (RTM0AC0000ADMP3MZ1SL41C) -#DISTRO_FEATURES_append = " mp3dec_lib" -#DISTRO_FEATURES_append = " mp3dec_mdw" - -# OMX WMA decoder library for Linux (RTM0AC0000XAWMAD30SL41C), -# WMA decoder middleware library for Linux (RTM0AC0000ADWMAMZ1SL41C) -#DISTRO_FEATURES_append = " wmadec_lib" -#DISTRO_FEATURES_append = " wmadec_mdw" - -# OMX AAC-LC encoder library for Linux (RTM0AC0000XAAACE30SL41C) -# AAC-LC encoder middleware library for Linux (RTM0AC0000AEAACMZ1SL41C) -#DISTRO_FEATURES_append = " aaclcenc_lib" -#DISTRO_FEATURES_append = " aaclcenc_mdw" - -# OMX Dolby(R) Digital decoder library for Linux (RTM0AC0000XADD5D30SL41C), -# Dolby(R) Digital decoder middleware library for Linux (RTM0AC0000ADDD5MZ1SL41C) -#DISTRO_FEATURES_append = " dddec_lib" -#DISTRO_FEATURES_append = " dddec_mdw" - -# OMX Media Component VP8 Decoder Library for Linux (RTM0AC0000XVVP8D30SL41C) -#DISTRO_FEATURES_append = " vp8dec_lib" - -# OMX Media Component VP8 Encoder Library for Linux (RTM0AC0000XVVP8E30SL41C) -#DISTRO_FEATURES_append = " vp8enc_lib" - -# OMX Media Component VP9 Decoder Library for Linux (RTM0AC0000XVVP9D30SL41C) -#DISTRO_FEATURES_append = " vp9dec_lib" - -# CMS Basic Color Management Middleware for Linux (RTM0AC0000JRCMBCV0SL41C) -#DISTRO_FEATURES_append = " cmsbcm" - -# CMS CMM3 Backlight Control Middleware for Linux (RTM0AC0000JRCMBLC0SL41C) -#DISTRO_FEATURES_append = " cmsblc" - -# CMS VSP2 Dynamic Gamma Correction Middleware for Linux (RTM0AC0000JRCMDGV0SL41C) -#DISTRO_FEATURES_append = " cmsdgc" - -# ISDB-T DTV Software Package for Linux (RTM0RC0000TE020000SL41C) -#DISTRO_FEATURES_append = " dtv" - -# DVD Core-Middleware for Linux (RTM0RC0000XDVDC301SL41C) -# DVD Encryption Library for Linux (RTM0RC0000XDVDF301SL41C) -#DISTRO_FEATURES_append = " dvd" -#DISTRO_FEATURES_append = " dvd_encryption_library" - -# ADSP Driver for Linux (RCG3AHPDL4101ZDO) -# ADSP Interface for Linux (RCG3AHIFL4101ZDP) -# ADSP Framework (RCG3AHFWN0201ZDP) -#DISTRO_FEATURES_append = " adsp" - -# AVB Software Package for Linux -#DISTRO_FEATURES_append = " avb" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Evaluation packages -#DISTRO_FEATURES_append = " use_eva_pkg" - -# Configuration for ivi-shell and ivi-extension -#DISTRO_FEATURES_append = " ivi-shell" - -# Configuration for USB 3.0 -#MACHINE_FEATURES_append = " usb3" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/bsp/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/bsp/bblayers.conf deleted file mode 100644 index 3b2c068a..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/bsp/bblayers.conf +++ /dev/null @@ -1,15 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - ${TOPDIR}/../meta-linaro/meta-optee \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/bsp/local-ltp.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/bsp/local-ltp.conf deleted file mode 100644 index cfff0538..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/bsp/local-ltp.conf +++ /dev/null @@ -1,284 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone-yocto" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "salvator-x" - -# This sets the SoC -# H3: r8a7795, M3: r8a7796, M3N: r8a77965 -SOC_FAMILY = "r8a7795" -#SOC_FAMILY = "r8a7796" -#SOC_FAMILY = "r8a77965" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks tools-sdk" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - -# -# Yocto Project SState Mirror -# -# The Yocto Project has prebuilt artefacts available for its releases, you can enable -# use of these by uncommenting the following line. This will mean the build uses -# the network to check for artefacts at the start of builds, which does slow it down -# equally, it will also speed up the builds by not having to build things if they are -# present in the cache. It assumes you can download something faster than you can build it -# which will depend on your network. -# -#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH" - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl2-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl2-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl2-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Mask graphic Pkgs -BBMASK .= "|gles-user-module|kernel-module-gles|wayland-kms|libgbm" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Configuration for USB 3.0 -#MACHINE_FEATURES_append = " usb3" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" - -# Additional packages for LTP -DISTRO_FEATURES_append = " pam" -CORE_IMAGE_EXTRA_INSTALL_append = " ltp" -IMAGE_INSTALL_append = " binutils elfutils file quota tar bzip2 sudo shadow glibc-utils net-tools procps cdrkit kernel-modules" - diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/bsp/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/bsp/local-wayland.conf deleted file mode 100644 index 9b28b4e1..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/bsp/local-wayland.conf +++ /dev/null @@ -1,288 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone-yocto" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "salvator-x" - -# This sets the SoC -# H3: r8a7795, M3: r8a7796, M3N: r8a77965 -SOC_FAMILY = "r8a7795" -#SOC_FAMILY = "r8a7796" -#SOC_FAMILY = "r8a77965" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - -# -# Yocto Project SState Mirror -# -# The Yocto Project has prebuilt artefacts available for its releases, you can enable -# use of these by uncommenting the following line. This will mean the build uses -# the network to check for artefacts at the start of builds, which does slow it down -# equally, it will also speed up the builds by not having to build things if they are -# present in the cache. It assumes you can download something faster than you can build it -# which will depend on your network. -# -#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH" - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl2-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl2-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl2-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# for Wayland/Weston weston-laucher -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" - -# Mask the wayland related to GFX -BBMASK .= "|gles-user-module|kernel-module-gles|wayland-kms|libgbm" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Mask the gstreamer recipe for MMP -BBMASK .= "|meta-renesas/meta-rcar-gen3/recipes-multimedia/gstreamer" - -# Add for gstreamer plugins ugly -LICENSE_FLAGS_WHITELIST = "commercial" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Configuration for USB 3.0 -#MACHINE_FEATURES_append = " usb3" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/bsp/local.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/bsp/local.conf deleted file mode 100644 index 33c4cc2d..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/bsp/local.conf +++ /dev/null @@ -1,281 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone-yocto" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "salvator-x" - -# This sets the SoC -# H3: r8a7795, M3: r8a7796, M3N: r8a77965 -SOC_FAMILY = "r8a7795" -#SOC_FAMILY = "r8a7796" -#SOC_FAMILY = "r8a77965" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - -# -# Yocto Project SState Mirror -# -# The Yocto Project has prebuilt artefacts available for its releases, you can enable -# use of these by uncommenting the following line. This will mean the build uses -# the network to check for artefacts at the start of builds, which does slow it down -# equally, it will also speed up the builds by not having to build things if they are -# present in the cache. It assumes you can download something faster than you can build it -# which will depend on your network. -# -#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH" - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl2-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl2-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl2-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Mask graphic Pkgs -BBMASK .= "|gles-user-module|kernel-module-gles|wayland-kms|libgbm" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Enable pam distro feature -DISTRO_FEATURES_append = " pam" - -# Configuration for USB 3.0 -#MACHINE_FEATURES_append = " usb3" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/gfx-only/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/gfx-only/bblayers.conf deleted file mode 100644 index 882db523..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/gfx-only/bblayers.conf +++ /dev/null @@ -1,15 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/gfx-only/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/gfx-only/local-wayland.conf deleted file mode 100644 index ea63a57c..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/gfx-only/local-wayland.conf +++ /dev/null @@ -1,294 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone-yocto" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "salvator-x" - -# This sets the SoC -# H3: r8a7795, M3: r8a7796, M3N: r8a77965 -SOC_FAMILY = "r8a7795" -#SOC_FAMILY = "r8a7796" -#SOC_FAMILY = "r8a77965" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - -# -# Yocto Project SState Mirror -# -# The Yocto Project has prebuilt artefacts available for its releases, you can enable -# use of these by uncommenting the following line. This will mean the build uses -# the network to check for artefacts at the start of builds, which does slow it down -# equally, it will also speed up the builds by not having to build things if they are -# present in the cache. It assumes you can download something faster than you can build it -# which will depend on your network. -# -#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH" - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl2-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl2-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl2-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Enable Gfx Pkgs -MACHINE_FEATURES_append = " gsx" -MULTI_PROVIDER_WHITELIST += "virtual/libgl virtual/egl virtual/libgles1 virtual/libgles2" - -# for Wayland/Weston -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" -PREFERRED_PROVIDER_virtual/libgles1 = "" -PREFERRED_PROVIDER_virtual/libgles2 = "gles-user-module" -PREFERRED_PROVIDER_virtual/egl = "libegl" -PREFERRED_PROVIDER_virtual/libgl = "" -PREFERRED_PROVIDER_virtual/mesa = "" -PREFERRED_PROVIDER_virtual/libgbm = "libgbm" -PREFERRED_PROVIDER_libgbm-dev = "libgbm" -BBMASK .= "|mesa-gl" -# Mask MMP recipes -BBMASK .= "|kernel-module-uvcs-drv|omx-user-module" - -# Add for gstreamer plugins ugly -LICENSE_FLAGS_WHITELIST = "commercial" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Configuration for USB 3.0 -#MACHINE_FEATURES_append = " usb3" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/mmp/bblayers.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/mmp/bblayers.conf deleted file mode 100644 index 882db523..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/mmp/bblayers.conf +++ /dev/null @@ -1,15 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ${TOPDIR}/../poky/meta \ - ${TOPDIR}/../poky/meta-poky \ - ${TOPDIR}/../poky/meta-yocto-bsp \ - ${TOPDIR}/../meta-renesas/meta-rcar-gen3 \ - ${TOPDIR}/../meta-linaro/meta-optee \ - ${TOPDIR}/../meta-openembedded/meta-oe \ - " diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/mmp/local-wayland.conf b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/mmp/local-wayland.conf deleted file mode 100644 index 91f3c163..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/conf/salvator-x/poky-gcc/mmp/local-wayland.conf +++ /dev/null @@ -1,403 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at local.conf.extended -# which contains other examples of configuration which can be placed in this file -# but new users likely won't need any of them initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone-yocto" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "mpc8315e-rdb" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= "salvator-x" - -# This sets the SoC -# H3: r8a7795, M3: r8a7796, M3N: r8a77965 -SOC_FAMILY = "r8a7795" -#SOC_FAMILY = "r8a7796" -#SOC_FAMILY = "r8a77965" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "poky" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -# - 'image-mklibs' to reduce shared library files size for an image -# - 'image-prelink' in order to prelink the filesystem image -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended -USER_CLASSES ?= "buildstats image-mklibs image-prelink" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. To -# enable this uncomment this line. See classes/testimage(-auto).bbclass for -# further details. -#TEST_IMAGE = "1" -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necesary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - ABORT,${TMPDIR},100M,1K \ - ABORT,${DL_DIR},100M,1K \ - ABORT,${SSTATE_DIR},100M,1K \ - ABORT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as http or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ -#file://.* file:///some/local/dir/sstate/PATH" - -# -# Yocto Project SState Mirror -# -# The Yocto Project has prebuilt artefacts available for its releases, you can enable -# use of these by uncommenting the following line. This will mean the build uses -# the network to check for artefacts at the start of builds, which does slow it down -# equally, it will also speed up the builds by not having to build things if they are -# present in the cache. It assumes you can download something faster than you can build it -# which will depend on your network. -# -#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH" - -# -# Qemu configuration -# -# By default qemu will build with a builtin VNC server where graphical output can be -# seen. The two lines below enable the SDL backend too. By default libsdl2-native will -# be built, if you want to use your host's libSDL instead of the minimal libsdl built -# by libsdl2-native then uncomment the ASSUME_PROVIDED line below. -PACKAGECONFIG_append_pn-qemu-native = " sdl" -PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" -#ASSUME_PROVIDED += "libsdl2-native" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "1" - -# Add systemd configuration -DISTRO_FEATURES_append = " systemd" -VIRTUAL-RUNTIME_init_manager = "systemd" - -# add the static lib to SDK toolchain -SDKIMAGE_FEATURES_append = " staticdev-pkgs" - -# Disable optee in meta-linaro layer -BBMASK = "meta-linaro/meta-optee/recipes-security/optee" - -# Enable Gfx Pkgs -MACHINE_FEATURES_append = " gsx" -MULTI_PROVIDER_WHITELIST += "virtual/libgl virtual/egl virtual/libgles1 virtual/libgles2" - -# for Wayland/Weston -DISTRO_FEATURES_NATIVESDK_append = " wayland" -DISTRO_FEATURES_append = " pam" -PREFERRED_PROVIDER_virtual/libgles1 = "" -PREFERRED_PROVIDER_virtual/libgles2 = "gles-user-module" -PREFERRED_PROVIDER_virtual/egl = "libegl" -PREFERRED_PROVIDER_virtual/libgl = "" -PREFERRED_PROVIDER_virtual/mesa = "" -PREFERRED_PROVIDER_virtual/libgbm = "libgbm" -PREFERRED_PROVIDER_libgbm-dev = "libgbm" -BBMASK .= "|mesa-gl" - -# Enable Multimedia features -MACHINE_FEATURES_append = " multimedia" - -# for gstreamer omx plugins -LICENSE_FLAGS_WHITELIST = "commercial" -# for mmp test program -DISTRO_FEATURES_append = " mm-test" - -# for weston v4l2 renderer -#DISTRO_FEATURES_append = " v4l2-renderer" - -# OMX H263 decoder library for Linux (RTM0AC0000XV263D30SL41C) -#DISTRO_FEATURES_append = " h263dec_lib" - -# OMX H264 decoder library for Linux (RTM0AC0000XV264D30SL41C) -DISTRO_FEATURES_append = " h264dec_lib" - -# OMX H264 encoder library for Linux (RTM0AC0000XV264E30SL41C) -#DISTRO_FEATURES_append = " h264enc_lib" - -# OMX H265 decoder library for Linux (RTM0AC0000XV265D30SL41C) -#DISTRO_FEATURES_append = " h265dec_lib" - -# OMX MPEG2 decoder library for Linux (RTM0AC0000XVM2VD30SL41C) -#DISTRO_FEATURES_append = " mpeg2dec_lib" - -# OMX Media Component MPEG4 Decoder Library for Linux (RTM0AC0000XVM4VD30SL41C) -#DISTRO_FEATURES_append = " mpeg4dec_lib" - -# OMX Media Component VC-1 Decoder Library for Linux (RTM0AC0000XVVC1D30SL41C) -#DISTRO_FEATURES_append = " vc1dec_lib" - -# OMX Media Component DivXD Decoder Library for Linux (RTM0AC0000XVDVXD30SL41C) -#DISTRO_FEATURES_append = " divxdec_lib" - -# OMX Media Component RealVideo Decoder Library for Linux (RTM0AC0000XVRLVD30SL41C) -#DISTRO_FEATURES_append = " rvdec_lib" - -# OMX Media Component ALAC Decoder Library for Linux (RTM0AC0000XAALAD30SL41C) -#DISTRO_FEATURES_append = " alacdec_lib" - -# OMX Media Component FLAC Decoder Library for Linux (RTM0AC0000XAFLAD30SL41C) -#DISTRO_FEATURES_append = " flacdec_lib" - -# OMX AAC-LC decoder library for Linux (RTM0AC0000XAAACD30SL41C), -# AAC-LC 2ch decoder middleware library for Linux (RTM0AC0000ADAACMZ1SL41C) -DISTRO_FEATURES_append = " aaclcdec_lib" -DISTRO_FEATURES_append = " aaclcdec_mdw" - -# OMX aacPlus V2 decoder library for Linux (RTM0AC0000XAAAPD30SL41C), -# aacPlus V2 decoder middleware library for Linux (RTM0AC0000ADAAPMZ1SL41C) -#DISTRO_FEATURES_append = " aacpv2dec_lib" -#DISTRO_FEATURES_append = " aacpv2dec_mdw" - -# OMX MP3 decoder library for Linux (RTM0AC0000XAMP3D30SL41C), -# MP3 decoder middleware library for Linux (RTM0AC0000ADMP3MZ1SL41C) -#DISTRO_FEATURES_append = " mp3dec_lib" -#DISTRO_FEATURES_append = " mp3dec_mdw" - -# OMX WMA decoder library for Linux (RTM0AC0000XAWMAD30SL41C), -# WMA decoder middleware library for Linux (RTM0AC0000ADWMAMZ1SL41C) -#DISTRO_FEATURES_append = " wmadec_lib" -#DISTRO_FEATURES_append = " wmadec_mdw" - -# OMX AAC-LC encoder library for Linux (RTM0AC0000XAAACE30SL41C) -# AAC-LC encoder middleware library for Linux (RTM0AC0000AEAACMZ1SL41C) -#DISTRO_FEATURES_append = " aaclcenc_lib" -#DISTRO_FEATURES_append = " aaclcenc_mdw" - -# OMX Dolby(R) Digital decoder library for Linux (RTM0AC0000XADD5D30SL41C), -# Dolby(R) Digital decoder middleware library for Linux (RTM0AC0000ADDD5MZ1SL41C) -#DISTRO_FEATURES_append = " dddec_lib" -#DISTRO_FEATURES_append = " dddec_mdw" - -# OMX Media Component VP8 Decoder Library for Linux (RTM0AC0000XVVP8D30SL41C) -#DISTRO_FEATURES_append = " vp8dec_lib" - -# OMX Media Component VP8 Encoder Library for Linux (RTM0AC0000XVVP8E30SL41C) -#DISTRO_FEATURES_append = " vp8enc_lib" - -# OMX Media Component VP9 Decoder Library for Linux (RTM0AC0000XVVP9D30SL41C) -#DISTRO_FEATURES_append = " vp9dec_lib" - -# CMS Basic Color Management Middleware for Linux (RTM0AC0000JRCMBCV0SL41C) -#DISTRO_FEATURES_append = " cmsbcm" - -# CMS CMM3 Backlight Control Middleware for Linux (RTM0AC0000JRCMBLC0SL41C) -#DISTRO_FEATURES_append = " cmsblc" - -# CMS VSP2 Dynamic Gamma Correction Middleware for Linux (RTM0AC0000JRCMDGV0SL41C) -#DISTRO_FEATURES_append = " cmsdgc" - -# ISDB-T DTV Software Package for Linux (RTM0RC0000TE020000SL41C) -#DISTRO_FEATURES_append = " dtv" - -# DVD Core-Middleware for Linux (RTM0RC0000XDVDC301SL41C) -# DVD Encryption Library for Linux (RTM0RC0000XDVDF301SL41C) -#DISTRO_FEATURES_append = " dvd" -#DISTRO_FEATURES_append = " dvd_encryption_library" - -# ADSP Driver for Linux (RCG3AHPDL4101ZDO) -# ADSP Interface for Linux (RCG3AHIFL4101ZDP) -# ADSP Framework (RCG3AHFWN0201ZDP) -#DISTRO_FEATURES_append = " adsp" - -# AVB Software Package for Linux -#DISTRO_FEATURES_append = " avb" - -# Linux ICCOM driver (RCG3ZLIDL4101ZNO) -# Linux ICCOM library (RCG3ZLILL4101ZNO) -#DISTRO_FEATURES_append = " iccom" - -# Evaluation packages -#DISTRO_FEATURES_append = " use_eva_pkg" - -# Configuration for ivi-shell and ivi-extension -#DISTRO_FEATURES_append = " ivi-shell" - -# Configuration for USB 3.0 -#MACHINE_FEATURES_append = " usb3" - -# Add Capacity Aware migration Strategy (CAS) -MACHINE_FEATURES_append = " cas" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/copyscript/copy_evaproprietary_softwares.sh b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/copyscript/copy_evaproprietary_softwares.sh deleted file mode 100755 index fd867b34..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/copyscript/copy_evaproprietary_softwares.sh +++ /dev/null @@ -1,1032 +0,0 @@ -#!/bin/sh - -# Copyright (C) Renesas Electronics Corporation 2016-2018 All rights reserved. - -usage() -{ -cat << EOF - usage: `basename $0` [-f] [-d] source-directory - -f: fource copy. ignore md5check - -d: debug mode - - Ex) - `basename $0` -f my_package_dir -EOF -} - -##### MD5 list ##### -. `dirname $0`/md5list.txt - -##### Library List ##### -# Audio Library -# Please add omx audio library to "_audio_list" -# Don't use space in xxx_name. -# audio_list="<software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name>" -_audio_list="AAC-LC_decoder_lib,EVARTM0AC0000XAAACD30SL41C,RTM0AC0000XAAACD30SL41C.tar.gz \ - AAC-LC_encoder_lib,EVARTM0AC0000XAAACE30SL41C,RTM0AC0000XAAACE30SL41C.tar.gz" - -# Audio M/W Library -# Please add omx audio library to "_audio_mw_list" -# Don't use space in xxx_name. -# audio_mw_list="<software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name>" -_audio_mw_list="AAC-LC_decoder_M/W,EVARTM0AC0000ADAACMZ1SL41C,RTM0AC0000ADAACMZ1SL41C.tar.gz \ - AAC-LC_encoder_M/W,EVARTM0AC0000AEAACMZ1SL41C,RTM0AC0000AEAACMZ1SL41C.tar.gz" - -# Video Decoder Library -# Please add omx video decoder library to "_video_dec_list" -# Don't use space in xxx_name. -# video_dec_list="<software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name>" -_video_dec_list="H264_decoder,EVARTM0AC0000XV264D30SL41C,EVARTM0AC0000XV264D30SL41C.tar.bz2" - -# Video Encoder Library -# Please add omx video encoder library to "_video_enc_list" -# Don't use space in xxx_name. -# video_enc_list="<software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name>" -_video_enc_list="H264_encoder,EVARTM0AC0000XV264E30SL41C,EVARTM0AC0000XV264E30SL41C.tar.bz2" - -# Common library packages -# Don't use space in xxx_name. -# XXX_list="<software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name>" -_omx_common_list="omx_common_lib,EVARTM0AC0000XCMCTL30SL41C,EVARTM0AC0000XCMCTL30SL41C.tar.bz2" -_uvcs_list="uvcs_lib,RCG3VUDRL4101ZDO,RCG3VUDRL4101ZDO.tar.bz2" -_video_enc_common_list="video_enc_common,EVARTM0AC0000XVCMNE30SL41C,EVARTM0AC0000XVCMNE30SL41C.tar.bz2" -_video_dec_common_list="video_dec_common,EVARTM0AC0000XVCMND30SL41C,EVARTM0AC0000XVCMND30SL41C.tar.bz2" -_audio_common_list="audio_common,EVARTM0AC0000XACMND30SL41C,RTM0AC0000XACMND30SL41C.tar.gz" - -# GFX -# Please add GFX to "_gfx_list" -# Don't use space in xxx_name. -# gfx_list="<package_name(user)>,<copy_file_name(user)>,<package_name(kernel)>,<copy_file_name(kernel)> \ -# <package_name(user)>,<copy_file_name(user)>,<package_name(kernel)>,<copy_file_name(kernel)> \ -# <package_name(user)>,<copy_file_name(user)>,<package_name(kernel)>,<copy_file_name(kernel)>" -_gfx_list="EVARTM0RC7795GLPG0001SL41C,EVA_r8a77951_linux_gsx_binaries_gles.tar.bz2,RCH3G001L4101ZDO,GSX_KM_H3.tar.bz2 \ - EVARTM0RC7796GLPG0001SL41C,EVA_r8a77960_linux_gsx_binaries_gles.tar.bz2,RCM3G001L4101ZDO,GSX_KM_M3.tar.bz2" - -##### static value -_MODE_ZIP=1 -_MODE_TAR=2 -_GFX_KM_INST_DIR="../meta-rcar-gen3/recipes-kernel/kernel-module-gles/kernel-module-gles" -_GFX_UM_INST_DIR="../meta-rcar-gen3/recipes-graphics/gles-module/gles-user-module" -_UVCS_INST_DIR="../meta-rcar-gen3/recipes-kernel/kernel-module-uvcs/kernel-module-uvcs-drv" -_OMX_UM_INST_DIR="../meta-rcar-gen3/recipes-multimedia/omx-module/omx-user-module" - -##### common function - -# $1: search file name -# $2: search directory -# return global variable -# _find_filename: find filename -# _extract_mode: _MODE_ZIP or _MODE_TAR -func_cmn_find_file() -{ -# echo "$1" -# echo "$2" - if [ -z "$1" ]; then - func_error "ERROR: func_cmn_find_file: empty filename" - fi - - if [ -z "$2" ]; then - _search_dir=${_src_full} - else - _search_dir=$2 - fi - - # search zip file -# zip_count=`find ${_search_dir} -maxdepth 1 -name "$1*.zip" | wc -l` - zip_count=`ls ${_search_dir}/$1*.zip 2>/dev/null | wc -l` - - # search tar file -# tar_count=`find ${_search_dir} -maxdepth 1 -name "$1*.tar.*" | wc -l` - tar_count=`ls ${_search_dir}/$1*.tar.* 2>/dev/null | wc -l` - - # duplicate file check - if [ 1 -lt `expr $zip_count + $tar_count` ]; then - echo "file1_zip = $zip_count" - echo "file1_tar = $tar_count" - func_error "ERROR: $1: too many files" - fi - - # set result - if [ 1 = $zip_count ]; then - _find_filename=$(ls ${_search_dir}/$1*.zip) - _extract_mode=${_MODE_ZIP} - elif [ 1 = $tar_count ]; then - _find_filename=$(ls ${_search_dir}/$1*.tar.*) - _extract_mode=${_MODE_TAR} - else - _find_filename="" - fi -} - -# $1: Mode -# $2: archive file name -func_cmn_extract_archive() -{ - case $1 in - $_MODE_ZIP) -# echo "Zip mode" - unzip -oq $2 - ;; - $_MODE_TAR) -# echo "Tar mode" - tar xf $2 - ;; - *) - func_error "ERROR: func_cmn_extract_archive: mode error." - exit 1 - ;; - esac -} - -# $1: set target filename. -# $2: set MD5 expectation value. -func_cmn_md5_check() -{ - _md5_func_param_filename=$1 - _md5_func_param_expectation=$2 - if [ ! -e ${_md5_func_param_filename} ]; then - func_error "func_cmn_md5_check : ERROR ${_md5_func_param_filename} not found." - fi - - _calc_md5=$(md5sum ${_md5_func_param_filename} | cut -d " " -f1) - - if [ -n "${_no_md5check}" ] || [ -z ${_md5_func_param_expectation} ]; then - echo "Skip MD5 : `basename ${_md5_func_param_filename}`" - return - fi - - if [ -n "${_debug}" ]; then - echo "MD5 target file = ${_md5_func_param_filename}" - echo "calc_md5 = ${_calc_md5}" - echo "expect_value = ${_md5_func_param_expectation}" - fi - - if [ ${_calc_md5} = ${_md5_func_param_expectation} ]; then - echo "MD5 OK : `basename ${_md5_func_param_filename}`" - else - echo "calc_md5 = ${_calc_md5}" - echo "expect_value = ${_md5_func_param_expectation}" - func_error "MD5 ERROR : ${_md5_func_param_filename}" - fi -} - -##### Error function -# $1: error message -func_error() -{ - echo "$1" - # cleanup temp directory. - func_clean_tempdir - exit 1 -} - -##### cleanup temp directory -func_clean_tempdir() -{ - echo "cleanup temp directory" - rm -rf ${TMPWORK} -} - -##### Template function for Single package - -# $1: package name -# $2: search target filename -# $3: search directory (full path) -# return -# _find_filename : the found file (full path) -# _extract_top_dir_name -func_search_file_in_package() -{ - # search package file - func_cmn_find_file $1 $3 - if [ -n "${_debug}" ]; then - echo "" - echo "FileName = ${_find_filename}" - echo "Mode = ${_extract_mode}" - fi - - if [ -z "${_find_filename}" ]; then - return - fi - - # extract - func_cmn_extract_archive ${_extract_mode} "${_find_filename}" - - # Get directory name - # {PATH}/Package_Version.tar.gz or XXXX.zip --> Package_Version - top_dir=$(basename ${_find_filename}) - top_dir=${top_dir%.*} - - # search file - num=`find ${top_dir} -name $2 | wc -l` - if [ ${num} -eq 1 ]; then - _find_filename=`find ${top_dir} -name $2` - else - # same filename exists. - _find_filename=`find ${top_dir} -name $2 | grep Software` - fi - - # set mode - if [ `echo ${_find_filename} | grep '\.'zip` ]; then - _extract_mode=${_MODE_ZIP} - else - _extract_mode=${_MODE_TAR} - fi - - # set return value - _extract_top_dir_name=${top_dir} -} - -# $1: package name -# $2: copy filename (md5 target) -# $3: expect MD5 value -# $4: search directory (full path) -# return -# _find_file_name -# _extract_top_dir_name -func_search_and_md5check() -{ - # search package file - func_cmn_find_file $1 $4 - if [ -n "${_debug}" ]; then - echo "" - echo "FileName = ${_find_filename}" - echo "Mode = ${_extract_mode}" - fi - - if [ -z "${_find_filename}" ]; then - return - fi - - # extract - func_cmn_extract_archive ${_extract_mode} "${_find_filename}" - - # MD5 - # Get directory name - # {PATH}/Package_Version.tar.gz or XXXX.zip --> Package_Version - top_dir=$(basename ${_find_filename}) - top_dir=${top_dir%.*} - - # call func_cmn_md5_check -# func_cmn_md5_check "${top_dir}/$1/Software/$2" "$3" - - # set return value - _extract_top_dir_name=${top_dir} -} - -##### Template function for Group package -# $1: group package name -# $2: single package name -# $3: copy filename (md5 target) -# $4: expect MD5 value -# $5: search directory (full path) -# return -# _find_file_name -# _extract_top_dir_name -# -# NOTE) This function support level1 packaging. "grp pkg in grp pkg" dose note support. -func_search_and_md5check_grp() -{ - # search group package @SRCDIR - func_cmn_find_file $1 $5 - if [ -n "${_debug}" ]; then - echo "search group package" - echo "FileName = ${_find_filename}" - echo "Mode = ${_extract_mode}" - echo "" - fi - - if [ -z "${_find_filename}" ]; then - return - fi - - # extract group package @TMPWORK - func_cmn_extract_archive ${_extract_mode} "${_find_filename}" - - cd ${_find_filename} - # check group pachage structure - # <Package name>_<version>/Package_Info.txt - top_dir=$(basename ${_find_filename}) - top_dir=${top_dir%.*} - - if [ ! -e ${top_dir}/Package_Info.txt ]; then - echo "grp package = $1" - echo "single package = $2" - func_error "ERROR: Package_Info.txt not found in Group package." - fi - - # search single package @TMPWORK/TOPDIR/<Group Package name>/ - func_cmn_find_file $2 "${TMPWORK}/${top_dir}/$1" - if [ -n "${_debug}" ]; then - echo "search single package" - echo "FileName = ${_find_filename}" - echo "Mode = ${_extract_mode}" - echo "" - fi - - if [ -z "${_find_filename}" ]; then - return - fi - - # mv <single package> TMPWORK/. - mv ${_find_filename} ${TMPWORK}/. - - # delete group package - rm -rf ${TMPWORK}/${top_dir} - - # call search and md5check @TMPWORK - func_search_and_md5check $2 $3 $4 ${TMPWORK} -} - -##### File search and MD5check for Package list -# $1: package list -# $2: rigid flag (1: true, other: false) -# -# return -# 1: [Success] One or more files were found. -# 0: [Fail] File not found -# -# package list format -# list ="<software_name>,<package_name>,<copy_file_name>,<md5_variable_name> \ -# <software_name>,<package_name>,<copy_file_name>,<md5_variable_name> \ -# <software_name>,<package_name>,<copy_file_name>,<md5_variable_name>" -# -# Note) Don't use space in xxx_name. -# Note) md5_variable_name is defined in md5list.txt. -# Prefix "_MD5_" is added automaticary. ex) FOO --> _MD5_FOO -# It is omissible. The default is "_MD5_<package_name>". -func_list_search_and_md5check () -{ - find_flag=0 - - for i in $1 - do - sw_name=`echo $i | cut -d "," -f 1` - pkg_name=`echo $i | cut -d "," -f 2` - copyfile_name=`echo $i | cut -d "," -f 3` - md5_val=`echo $i | cut -d "," -f 4` - - # <MD5_name> is empty. Default MD5 name is "_MD5_<pkg_name>" - if [ -z "${md5_val}" ]; then - md5_val=`eval echo '$_MD5_'${pkg_name}` - else - md5_val=`eval echo '$_MD5_'${md5_val}` - fi - - if [ -n "${_debug}" ]; then - echo "" - echo "sw_name = $sw_name" - echo "pkg_name = $pkg_name" - echo "copyfile_name = $copyfile_name" - echo "md5_val = $md5_val" - fi - - func_search_and_md5check "${pkg_name}" "${copyfile_name}" "${md5_val}" "${_src_full}" - if [ -z "${_find_filename}" ]; then - echo "${sw_name} not found!" - # rigid flag = TRUE. Not found = ERROR - if [ "X$2" = "X1" ]; then - return 0 - fi - else - find_flag=1 - fi - done - - return ${find_flag} -} - -##### File search and install (without MD5check) for Package list -# -# $1: package list -# $2: install directory -# -# return -# 1: [Success] One or more files were installed. -# 0: [Fail] File not found -# -# package list format -# list ="<software_name>,<package_name>,<copy_file_name>,<md5_variable_name> \ -# <software_name>,<package_name>,<copy_file_name>,<md5_variable_name> \ -# <software_name>,<package_name>,<copy_file_name>,<md5_variable_name>" -# -# Note) Don't use space in xxx_name. -# Note) md5_variable_name is defined in md5list.txt. -# Prefix "_MD5_" is added automaticary. ex) FOO --> _MD5_FOO -# It is omissible. The default is "_MD5_<package_name>". -func_list_search_and_install_wo_md5check() -{ - find_flag=0 - - for i in $1 - do - sw_name=`echo $i | cut -d "," -f 1` - pkg_name=`echo $i | cut -d "," -f 2` - copyfile_name=`echo $i | cut -d "," -f 3` - md5_val=`echo $i | cut -d "," -f 4` - - # <MD5_name> is empty. Default MD5 name is "_MD5_<pkg_name>" - if [ -z "${md5_val}" ]; then - md5_val=`eval echo '$_MD5_'$pkg_name` - else - md5_val=`eval echo '$_MD5_'${md5_val}` - fi - - copyfile_name=$(basename ${copyfile_name}) - - if [ -n "${_debug}" ]; then - echo "" - echo "sw_name = $sw_name" - echo "pkg_name = $pkg_name" - echo "copyfile_name = $copyfile_name" - echo "md5_val = $md5_val" - fi - - # file search - func_search_file_in_package "${pkg_name}" "${copyfile_name}" "${_src_full}" - if [ -z "${_find_filename}" ]; then - echo "${sw_name} not found!" - else - find_flag=1 - - # install - install -d $2 - install -m 0644 ${_find_filename} $2 - echo "Installed $sw_name" - echo " : ${pkg_name}" - fi - done - - return ${find_flag} -} - -##### File search and install for Package list -# -# $1: package list -# $2: install directory -# -# return -# 1: [Success] One or more files were installed. -# 0: [Fail] File not found -# -# package list format -# list ="<software_name>,<package_name>,<copy_file_name>,<md5_variable_name> \ -# <software_name>,<package_name>,<copy_file_name>,<md5_variable_name> \ -# <software_name>,<package_name>,<copy_file_name>,<md5_variable_name>" -# -# Note) Don't use space in xxx_name. -# Note) md5_variable_name is defined in md5list.txt. -# Prefix "_MD5_" is added automaticary. ex) FOO --> _MD5_FOO -# It is omissible. The default is "_MD5_<package_name>". -func_list_search_and_install() -{ - find_flag=0 - - for i in $1 - do - sw_name=`echo $i | cut -d "," -f 1` - pkg_name=`echo $i | cut -d "," -f 2` - copyfile_name=`echo $i | cut -d "," -f 3` - md5_val=`echo $i | cut -d "," -f 4` - - # <MD5_name> is empty. Default MD5 name is "_MD5_<pkg_name>" - if [ -z "${md5_val}" ]; then - md5_val=`eval echo '$_MD5_'$pkg_name` - else - md5_val=`eval echo '$_MD5_'${md5_val}` - fi - - if [ -n "${_debug}" ]; then - echo "" - echo "sw_name = $sw_name" - echo "pkg_name = $pkg_name" - echo "copyfile_name = $copyfile_name" - echo "md5_val = $md5_val" - fi - - # seach & MD5 check - func_search_and_md5check "${pkg_name}" "${copyfile_name}" "${md5_val}" "${_src_full}" - if [ -z "${_find_filename}" ]; then - echo "${sw_name} not found!" - else - find_flag=1 - - # Get directory name - # _find_filename = pkg file (full path). It is not copyfile. - top_dir=$(basename ${_find_filename}) - top_dir=${top_dir%.*} - - # install - install -d $2 - install -m 0644 ${top_dir}/${pkg_name}/Software/${copyfile_name} $2 - echo "Installed $sw_name" - echo " : ${pkg_name}" - fi - done - - return ${find_flag} -} - -##### Package function - -# For 3D graphics packages -func_gfx() -{ - echo "" - echo "Copying for Graphic Packages" - - copy_flag=0 - - for i in ${_gfx_list} - do - user_pkg_name=`echo $i | cut -d "," -f 1` - user_copyfile_name=`echo $i | cut -d "," -f 2` - user_md5_val=`eval echo '$_MD5_'${user_pkg_name}` - kern_pkg_name=`echo $i | cut -d "," -f 3` - kern_copyfile_name=`echo $i | cut -d "," -f 4` - kern_md5_val=`eval echo '$_MD5_'${kern_pkg_name}` - - if [ -n "${_debug}" ]; then - echo "" - echo "user_pkg_name = ${user_pkg_name}" - echo "user_copyfile_name= ${user_copyfile_name}" - echo "user_md5_val = ${user_md5_val}" - echo "kern_pkg_name = ${kern_pkg_name}" - echo "kern_copyfile_name= ${kern_copyfile_name}" - echo "kern_md5_val = ${kern_md5_val}" - fi - - # user module (file1) - func_search_and_md5check "${user_pkg_name}" "${user_copyfile_name}" "${user_md5_val}" "${_src_full}" - - if [ -z "${_find_filename}" ]; then - echo "${user_pkg_name} not found!" - continue - fi - - file1_top_dir=${_extract_top_dir_name} - echo "file1 top : ${file1_top_dir}" - - # kernel module (file2) - func_search_and_md5check "${kern_pkg_name}" "${kern_copyfile_name}" "${kern_md5_val}" "${_src_full}" - - # file1 exist, but file2 not exist - if [ -z "${_find_filename}" ]; then - func_error "ERROR: func_gfx: package file for Graphic is incomplete." - fi - - file2_top_dir=${_extract_top_dir_name} - echo "file2 top : ${file2_top_dir}" - - # Finally copy is performed - copy_flag=1 - install -d ${_GFX_UM_INST_DIR} - install -m 0644 ${file1_top_dir}/${user_pkg_name}/Software/${user_copyfile_name} ${_GFX_UM_INST_DIR}/`echo ${user_copyfile_name} | cut -b 5-200` - install -d ${_GFX_KM_INST_DIR} - install -m 0644 ${file2_top_dir}/${kern_pkg_name}/Software/${kern_copyfile_name} ${_GFX_KM_INST_DIR} - echo "Installed GFX package" - echo " : ${user_pkg_name}" - echo " : ${kern_pkg_name}" - echo "" - done - - if [ ${copy_flag} -eq 0 ]; then - return - fi - - echo "" - echo "Packages for GFX module were found and copied." - echo /=======================================================/ -} - -##### For Multi Media - -# For Audio library copy -# -# Global -# _audio_list: audio library list -# Return -# 0: Not found -# 1: Success -func_audio_lib() -{ - # MD5 check: OMX Media Component Audio Common Library for Linux - func_list_search_and_md5check "${_audio_common_list}" "1" - if [ $? -eq 0 ]; then - echo "Audio Common Library not found!" - echo "" - return 0 - fi - - # MD5 check: audio library. - func_list_search_and_md5check "${_audio_list}" - if [ $? -eq 0 ]; then - # library not found. - echo "" - echo "Audio library not found." - return 0 - fi - - # Add audio common library to list - _audio_list="${_audio_common_list} ${_audio_list}" - - # Install omx common lib (if not installed) - func_install_omx_common - - # Install Audio library packages - func_list_search_and_install_wo_md5check "${_audio_list}" "${_OMX_UM_INST_DIR}" - _audio_common_install=1 - - return 1 -} - -# For Audio library -func_audio() -{ - echo "" - echo "Copying for Audio Common Packages" - - _audio_common_install=0 - - # Audio requires OMX common library - if [ ${_omx_common_install} -eq 0 ]; then - # MD5 check (rigid flag=TRUE) - func_list_search_and_md5check "${_omx_common_list}" "1" - if [ $? -eq 0 ]; then - echo "OMX Common Library not found!" - echo "" - return - fi - else - echo "OMX Common Library already installed" - fi - - # Audio Library - func_audio_lib - if [ $? -eq 0 ]; then - echo "" - echo "Skip Audio Packages" - echo "" - return - fi - - echo "" - echo "Packages for Audio module were found and copied." - echo /=======================================================/ -} - -# For Audio M/W -# Global -# _audio_mw_list: audio M/W library list -# Return -# 0: Not found -# 1: Success -func_audio_mw() -{ - echo "" - echo "Copying for Audio M/W Packages" - - # MD5 check - func_list_search_and_md5check "${_audio_mw_list}" - if [ $? -eq 0 ]; then - # library not found. - echo "" - echo "Packages for Audio M/W module were not found." - return 0 - fi - - # Install Audio M/W library packages - func_list_search_and_install_wo_md5check "${_audio_mw_list}" "${_OMX_UM_INST_DIR}" - - echo "" - echo "Packages for Audio M/W module were found and copied." - echo /=======================================================/ - - return 1 -} - -# install OMX common library -func_install_omx_common() -{ - if [ ${_omx_common_install} -eq 0 ]; then - echo "" - echo "Install for OMX Common Packages" - func_list_search_and_install_wo_md5check "${_omx_common_list}" "${_OMX_UM_INST_DIR}" - _omx_common_install=1 - fi -} - -# install uvcs driver -func_install_uvcs() -{ - if [ ${_uvcs_install} -eq 0 ]; then - echo "" - echo "Installed UVCS driver" - func_list_search_and_install_wo_md5check "${_uvcs_list}" "${_UVCS_INST_DIR}" - _uvcs_install=1 - fi -} - -# search & MD5 check for OMX Video Decoder library -# Global -# _video_dec_list: video decoder list -# Return -# 0: Not found -# 1: Success -func_video_decoder_lib() -{ - echo "" - echo "Copying for Video Decoder Library Packages" - - # MD5 check: Decoder Common Library (rigid flag=TRUE) - func_list_search_and_md5check "${_video_dec_common_list}" "1" - if [ $? -eq 0 ]; then - echo "OMX Video Decoder Common Library not found!" - return 0 - fi - - # MD5 check: Video Decoder Library - func_list_search_and_md5check "${_video_dec_list}" - if [ $? -eq 0 ]; then - # library not found. - return 0 - fi - - # install OMX common lib (if not installed) - func_install_omx_common - - # install UVCS driver (if not installed) - func_install_uvcs - - # Add video decoder common lib to list - _video_dec_list="${_video_dec_common_list} ${_video_dec_list}" - - # install searched library - func_list_search_and_install_wo_md5check "${_video_dec_list}" "${_OMX_UM_INST_DIR}" - _video_decoder_common_install=1 - - return 1 -} - -# search & MD5 check for OMX Video Encoder library -# Global -# _video_enc_list: video encoder list -# Return -# 0: Not found -# 1: Success -func_video_encoder_lib() -{ - echo "" - echo "Copying for Video Encoder Library Packages" - - - # MD5 check Encoder Common Library (rigid flag=TRUE) - func_list_search_and_md5check "${_video_enc_common_list}" "1" - if [ $? -eq 0 ]; then - echo "OMX Video Encoder Common Library not found!" - return 0 - fi - _video_encoder_common_install=0 - - # Video Encoder Library - # MD5 check - func_list_search_and_md5check "${_video_enc_list}" - if [ $? -eq 0 ]; then - # library not found. - return 0 - fi - - # install common lib (if not installed) - func_install_omx_common - - # install UVCS driver (if not installed) - func_install_uvcs - - # Add Video encoder common library to list - _video_enc_list="${_video_enc_common_list} ${_video_enc_list}" - - # install searched library - func_list_search_and_install_wo_md5check "${_video_enc_list}" "${_OMX_UM_INST_DIR}" - _video_encoder_common_install=1 - - return 1 -} - -# For Video decoder -# Global -# _video_dec_list: video decoder list -# Return -# 0: Not found -# 1: Success -func_video_decoder() -{ - echo "" - echo "Copying for Video Decoder Packages" - - # OMX Common library - if [ ${_omx_common_install} -eq 0 ]; then - # MD5 check (rigid flag=TRUE) - func_list_search_and_md5check "${_omx_common_list}" "1" - if [ $? -eq 0 ]; then - echo "OMX Common Library not found!" - echo "" - return - fi - else - echo "OMX Common Library already installed" - fi - - # UVCS driver - if [ ${_uvcs_install} -eq 0 ]; then - # MD5 check (rigid flag=TRUE) - func_list_search_and_md5check "${_uvcs_list}" "1" - if [ $? -eq 0 ]; then - echo "UVCS driver not found!" - echo "" - return - fi - else - echo "UVCS driver already installed" - fi - - # OMX Decoder - # Decoder common Lib - func_video_decoder_lib - if [ $? -eq 0 ]; then - echo "" - echo "Skip Video Decoder Packages" - echo "" - return - fi - - echo "" - echo "Packages for video decoder module were found and copied." - echo /=======================================================/ -} - -# For Video encoder -func_video_encoder() -{ - echo "" - echo "Copying for Video Encoder Packages" - - # OMX Common library - if [ ${_omx_common_install} -eq 0 ]; then - # MD5 check (rigid flag=TRUE) - func_list_search_and_md5check "${_omx_common_list}" "1" - if [ $? -eq 0 ]; then - echo "OMX Common Library not found!" - echo "" - return - fi - else - echo "OMX Common Library already installed" - fi - - # UVCS driver - if [ ${_uvcs_install} -eq 0 ]; then - # MD5 check (rigid flag=TRUE) - func_list_search_and_md5check "${_uvcs_list}" "1" - if [ $? -eq 0 ]; then - echo "UVCS driver not found!" - echo "" - return - fi - else - echo "UVCS driver already installed" - fi - - # OMX Encoder - # Encoder common Lib - func_video_encoder_lib - if [ $? -eq 0 ]; then - echo "" - echo "Skip Video Encoder Packages" - echo "" - return - fi - - echo "" - echo "Packages for video encoder module were found and copied." - echo /=======================================================/ -} - -################################ -# Copy Script Main routine -################################ -echo "Copyscript for R-Car Gen3" -echo -#### 1) Checking current directory -if [ ! -d meta-rcar-gen3 ]; then - echo "ERROR: Please extract meta-renesas and cd to it, before execute $0" - exit 1 -fi - -#### 2) Checking Arguments -if [ "X$1" = "X" ]; then - usage - exit 1 -fi - -while [ $# -gt 0 ] ; do - case "$1" in - -f|--force) - _no_md5check=1 - ;; - -d|--debug) - _debug=1 - ;; - *) - _src_dirname=$(basename $1) - _src_path=$(cd $(dirname $1) && pwd) - _src_full=${_src_path}/${_src_dirname} - ;; - esac - shift -done - -#### 3) Checking ClickThrough present - -COUNTFILE=$(ls ${_src_full}/R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-*.zip 2>/dev/null | wc --lines) -if [ ${COUNTFILE} -eq 0 ]; then - echo "R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-*.zip not found!" - usage - exit 1 -fi -if [ ${COUNTFILE} -gt 1 ]; then - echo "More than one (${COUNTFILE}) R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-*.zip file found!" - echo "Clean your directory \"${_src_full}\"" - exit 1 -fi - -COUNTFILE=$(ls ${_src_full}/R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-*.zip 2>/dev/null | wc --lines) -if [ ${COUNTFILE} -eq 0 ]; then - echo "R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-*.zip not found!" - exit 1 -fi -if [ ${COUNTFILE} -gt 1 ]; then - echo "More than one (${COUNTFILE}) R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-*.zip file found!" - echo "Clean your directory \"${_src_full}\"" - usage - exit 1 -fi - -unzip -d ${_src_full} -oq ${_src_full}/R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-*.zip -unzip -d ${_src_full} -oq ${_src_full}/R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-*.zip - -tar -C ${_src_full} -zxf ${_src_full}/R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-*.tar.gz --strip-components 2 -tar -C ${_src_full} -zxf ${_src_full}/R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-*.tar.gz --strip-components 2 - -# source directory check -if [ ! -d ${_src_path}/${_src_dirname} ]; then - echo "${_src_path}/${_src_dirname} not found." - usage - exit 1 -fi - -if [ -n "${_debug}" ]; then - echo "src = ${_src_dirname}" - echo "src_path = ${_src_path}" - echo "src_full = ${_src_full}" - echo "no_md5check = ${_no_md5check}" - echo "" -fi - -##### 3) create temp directory -TMPWORK=${PWD}/CP_SCRIPT_TEMP -if [ -d ${TMPWORK} ]; then - echo "ERROR: Work directory already exist." - exit 1 -fi -install -d -m 700 ${TMPWORK} -cd ${TMPWORK} - -##### 4) copy -# initialize flag -_omx_common_install=0 -_uvcs_install=0 -_audio_common_install=0 -_video_decoder_common_install=0 -_video_encoder_common_install=0 - -func_gfx -func_audio -func_audio_mw -func_video_decoder -func_video_encoder - -##### 5) cleanup temp directory -func_clean_tempdir - -##### End -echo "Complete copying !" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/copyscript/copy_proprietary_softwares.sh b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/copyscript/copy_proprietary_softwares.sh deleted file mode 100755 index 2ce4148b..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/copyscript/copy_proprietary_softwares.sh +++ /dev/null @@ -1,1329 +0,0 @@ -#!/bin/sh - -# Copyright (C) Renesas Electronics Corporation 2015-2018 All rights reserved. - -usage() -{ -cat << EOF - usage: `basename $0` [-f] [-d] source-directory - -f: fource copy. ignore md5check - -d: debug mode - - Ex) - `basename $0` -f my_package_dir -EOF -} - -##### MD5 list ##### -. `dirname $0`/md5list.txt - -##### Library List ##### -# Audio Library -# Please add omx audio library to "_audio_list" -# Don't use space in xxx_name. -# audio_list="<software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name>" -_audio_list="AAC-LC_decoder_lib,RTM0AC0000XAAACD30SL41C,RTM0AC0000XAAACD30SL41C.tar.gz \ - aacPlusV2_decoder_lib,RTM0AC0000XAAAPD30SL41C,RTM0AC0000XAAAPD30SL41C.tar.gz \ - MP3_decoder_lib,RTM0AC0000XAMP3D30SL41C,RTM0AC0000XAMP3D30SL41C.tar.gz \ - WMA_decoder_lib,RTM0AC0000XAWMAD30SL41C,RTM0AC0000XAWMAD30SL41C.tar.gz \ - AAC-LC_encoder_lib,RTM0AC0000XAAACE30SL41C,RTM0AC0000XAAACE30SL41C.tar.gz \ - ALAC_decoder_lib,RTM0AC0000XAALAD30SL41C,RTM0AC0000XAALAD30SL41C.tar.gz \ - FLAC_decoder_lib,RTM0AC0000XAFLAD30SL41C,RTM0AC0000XAFLAD30SL41C.tar.gz \ - Dolby_decoder_lib,RTM0AC0000XADD5D30SL41C,RTM0AC0000XADD5D30SL41C.tar.gz" - -# Audio M/W Library -# Please add omx audio library to "_audio_mw_list" -# Don't use space in xxx_name. -# audio_mw_list="<software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name>" -_audio_mw_list="AAC-LC_decoder_M/W,RTM0AC0000ADAACMZ1SL41C,RTM0AC0000ADAACMZ1SL41C.tar.gz \ - aacPlusV2_decoder_M/W,RTM0AC0000ADAAPMZ1SL41C,RTM0AC0000ADAAPMZ1SL41C.tar.gz \ - MP3_decoder_M/W,RTM0AC0000ADMP3MZ1SL41C,RTM0AC0000ADMP3MZ1SL41C.tar.gz \ - WMA_decoder_M/W,RTM0AC0000ADWMAMZ1SL41C,RTM0AC0000ADWMAMZ1SL41C.tar.gz \ - AAC-LC_encoder_M/W,RTM0AC0000AEAACMZ1SL41C,RTM0AC0000AEAACMZ1SL41C.tar.gz \ - DDD_decoder_M/W,RTM0AC0000ADDD5MZ1SL41C,RTM0AC0000ADDD5MZ1SL41C.tar.gz" - -# Video Decoder Library -# Please add omx video decoder library to "_video_dec_list" -# Don't use space in xxx_name. -# video_dec_list="<software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name>" -_video_dec_list="H263_decoder,RTM0AC0000XV263D30SL41C,RTM0AC0000XV263D30SL41C.tar.bz2 \ - H264_decoder,RTM0AC0000XV264D30SL41C,RTM0AC0000XV264D30SL41C.tar.bz2 \ - H265_decoder,RTM0AC0000XV265D30SL41C,RTM0AC0000XV265D30SL41C.tar.bz2 \ - MPEG2_decoder,RTM0AC0000XVM2VD30SL41C,RTM0AC0000XVM2VD30SL41C.tar.bz2 \ - MPEG4_decoder,RTM0AC0000XVM4VD30SL41C,RTM0AC0000XVM4VD30SL41C.tar.bz2 \ - VC1_decoder,RTM0AC0000XVVC1D30SL41C,RTM0AC0000XVVC1D30SL41C.tar.bz2 \ - DivX_decoder,RTM0AC0000XVDVXD30SL41C,RTM0AC0000XVDVXD30SL41C.tar.bz2 \ - RealVideo_decoder,RTM0AC0000XVRLVD30SL41C,RTM0AC0000XVRLVD30SL41C.tar.bz2 \ - VP8_decoder,RTM0AC0000XVVP8D30SL41C,RTM0AC0000XVVP8D30SL41C.tar.bz2 \ - VP9_decoder,RTM0AC0000XVVP9D30SL41C,RTM0AC0000XVVP9D30SL41C.tar.bz2" - -# Video Encoder Library -# Please add omx video encoder library to "_video_enc_list" -# Don't use space in xxx_name. -# video_enc_list="<software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name>" -_video_enc_list="H264_encoder,RTM0AC0000XV264E30SL41C,RTM0AC0000XV264E30SL41C.tar.bz2 \ - VP8_encoder,RTM0AC0000XVVP8E30SL41C,RTM0AC0000XVVP8E30SL41C.tar.bz2" - -# Common library packages -# Don't use space in xxx_name. -# XXX_list="<software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name>" -_omx_common_list="omx_common_lib,RTM0AC0000XCMCTL30SL41C,RTM0AC0000XCMCTL30SL41C.tar.bz2" -_uvcs_list="uvcs_lib,RCG3VUDRL4101ZDO,RCG3VUDRL4101ZDO.tar.bz2" -_video_enc_common_list="video_enc_common,RTM0AC0000XVCMNE30SL41C,RTM0AC0000XVCMNE30SL41C.tar.bz2" -_video_dec_common_list="video_dec_common,RTM0AC0000XVCMND30SL41C,RTM0AC0000XVCMND30SL41C.tar.bz2" -_audio_common_list="audio_common,RTM0AC0000XACMND30SL41C,RTM0AC0000XACMND30SL41C.tar.gz" - - -# DTV Library -# Please add DTV library to "_dtv_list" -# Don't use space in xxx_name. -# dtv_xx_list="<software_name>,<package_name>,<copy_file_name>,<MD5_name> \ -# <software_name>,<package_name>,<copy_file_name>,<MD5_name> \ -# <software_name>,<package_name>,<copy_file_name>,<MD5_name>" -_dtv_km_list="dtv_km,RCG3T001L4101ZDO,Software.tar.gz" -_dtv_um_list="dtv_lib,RTM0RC0000TE020000SL41C,Software.tar.gz,RTM0RC0000TE020000SL41C1 \ - dtv_userfunc,RTM0RC0000TE020000SL41C,../Reference/Reference.tar.gz,RTM0RC0000TE020000SL41C2" - -# DVD Library -# Please add DVD library to "_dvd_list" -# Don't use space in xxx_name. -# dvd_list="<software_name>,<package_name>,<copy_file_name>,<MD5_name> \ -# <software_name>,<package_name>,<copy_file_name>,<MD5_name> \ -# <software_name>,<package_name>,<copy_file_name>,<MD5_name>" -_dvd_list="dvd_lib,RTM0RC0000XDVDC301SL41C,Software.tar.gz \ - dvd_encrypt_lib,RTM0RC0000XDVDF301SL41C,Software.tar.gz" - -# CMS Library -# Please add CMS library to "_cms_list" -# Don't use space in xxx_name. -# cms_list="<software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name>" -_cms_list="bcm,RTM0AC0000JRCMBCV0SL41C,RTM0AC0000JRCMBCV0SL41C.tar.gz \ - blc,RTM0AC0000JRCMBLC0SL41C,RTM0AC0000JRCMBLC0SL41C.tar.gz \ - dgc,RTM0AC0000JRCMDGV0SL41C,RTM0AC0000JRCMDGV0SL41C.tar.gz" - -# ADSP -# Please add ADSP to "_adsp_list" -# Don't use space in xxx_name. -# adsp_xx_list="<software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name> \ -# <software_name>,<package_name>,<copy_file_name>" -_adsp_um_list="adsp_fw,RCG3AHFWN0201ZDP,RCG3AHFWN0201ZDP.tar.gz \ - adsp_if,RCG3AHIFL4101ZDP,RCG3AHIFL4101ZDP.tar.gz" -_adsp_km_list="adsp_driver,RCG3AHPDL4101ZDO,RCG3AHPDL4101ZDO.tar.gz" - -# GFX -# Please add GFX to "_gfx_list" -# Don't use space in xxx_name. -# gfx_list="<package_name(user)>,<copy_file_name(user)>,<package_name(kernel)>,<copy_file_name(kernel)> \ -# <package_name(user)>,<copy_file_name(user)>,<package_name(kernel)>,<copy_file_name(kernel)> \ -# <package_name(user)>,<copy_file_name(user)>,<package_name(kernel)>,<copy_file_name(kernel)>" -_gfx_list="RTM0RC7795GLPG0001SL41C,r8a77951_linux_gsx_binaries_gles.tar.bz2,RCH3G001L4101ZDO,GSX_KM_H3.tar.bz2 \ - RTM0RC7796GLPG0001SL41C,r8a77960_linux_gsx_binaries_gles.tar.bz2,RCM3G001L4101ZDO,GSX_KM_M3.tar.bz2 \ - RTM0RC7796GLPGB001SL41C,r8a77965_linux_gsx_binaries_gles.tar.bz2,RCN3G001L4101ZDO,GSX_KM_M3N.tar.bz2 \ - RTM0RC7799GLPG0001SL41C,r8a77990_linux_gsx_binaries_gles.tar.bz2,RCE3G001L4101ZDO,GSX_KM_E3.tar.bz2 \ - INFRTM0RC7795GLPG0001SL41C,INF_r8a77951_linux_gsx_binaries_gles.tar.bz2,RCH3G001L4101ZDO,GSX_KM_H3.tar.bz2 \ - INFRTM0RC7796GLPG0001SL41C,INF_r8a77960_linux_gsx_binaries_gles.tar.bz2,RCM3G001L4101ZDO,GSX_KM_M3.tar.bz2 \ - INFRTM0RC7796GLPGB001SL41C,INF_r8a77965_linux_gsx_binaries_gles.tar.bz2,RCN3G001L4101ZDO,GSX_KM_M3N.tar.bz2 \ - INFRTM0RC7799GLPG0001SL41C,INF_r8a77990_linux_gsx_binaries_gles.tar.bz2,RCE3G001L4101ZDO,GSX_KM_E3.tar.bz2" - -# ICCOM -# Please add ICCOM to "_iccom_list" -# Don't use space in xxx_name. -# iccom_xx_list="<software_name>,<package_name>,<copy_file_name>,<MD5_name> \ -# <software_name>,<package_name>,<copy_file_name>,<MD5_name> \ -# <software_name>,<package_name>,<copy_file_name>,<MD5_name>" -_iccom_km_list="iccom_mfis,RCG3ZLIDL4101ZNO,iccom-mfis.tar.bz2,RCG3ZLIDL4101ZNO1 \ - iccom_sample,RCG3ZLIDL4101ZNO,iccom-hwspinlock-sample.tar.bz2,RCG3ZLIDL4101ZNO2" -_iccom_um_list="iccom_lib,RCG3ZLILL4101ZNO,libiccom.tar.bz2,RCG3ZLILL4101ZNO" - -# Crypto Package list -# Please add crypto (zip) package name to "_crypto_pkg_list" -# Don't use space in xxx_name. -# crypto_pkg_list="<packgae name> <packgae name> <packgae name>" -_crypto_pkg_list="RTM0AC0000ADDD5MZ1SL41C" - -##### static value -_MODE_ZIP=1 -_MODE_TAR=2 -_MODE_CRYPTO_ZIP=3 -_GFX_KM_INST_DIR="../meta-rcar-gen3/recipes-kernel/kernel-module-gles/kernel-module-gles" -_GFX_UM_INST_DIR="../meta-rcar-gen3/recipes-graphics/gles-module/gles-user-module" -_UVCS_INST_DIR="../meta-rcar-gen3/recipes-kernel/kernel-module-uvcs/kernel-module-uvcs-drv" -_OMX_UM_INST_DIR="../meta-rcar-gen3/recipes-multimedia/omx-module/omx-user-module" -_DTV_KM_INST_DIR="../meta-rcar-gen3/recipes-kernel/kernel-module-dtv/files" -_DTV_UM_INST_DIR="../meta-rcar-gen3/recipes-multimedia/dtv-module/dtv-user-module" -_DVD_UM_INST_DIR="../meta-rcar-gen3/recipes-multimedia/dvd-module/dvd-user-module \ - ../meta-rcar-gen3/recipes-multimedia/dvd-module/dvd-encryption-module" -_CMS_UM_INST_DIR="../meta-rcar-gen3/recipes-multimedia/cms-module/cms-user-module" -_ADSP_KM_INST_DIR="../meta-rcar-gen3/recipes-kernel/kernel-module-adsp/xtensa-hifi" -_ADSP_UM_INST_DIR="../meta-rcar-gen3/recipes-multimedia/adsp-module/files" -_ICCOM_KM_INST_DIR="../meta-rcar-gen3/recipes-kernel/kernel-module-iccom/files" -_ICCOM_UM_INST_DIR="../meta-rcar-gen3/recipes-connectivity/iccom-module/files" - -##### common function - -# $1: search file name -# $2: search directory -# return global variable -# _find_filename: find filename -# _extract_mode: _MODE_ZIP or _MODE_TAR -func_cmn_find_file() -{ -# echo "$1" -# echo "$2" - if [ -z "$1" ]; then - func_error "ERROR: func_cmn_find_file: empty filename" - fi - - if [ -z "$2" ]; then - _search_dir=${_src_full} - else - _search_dir=$2 - fi - - # search zip file -# zip_count=`find ${_search_dir} -maxdepth 1 -name "$1*.zip" | wc -l` - zip_count=`ls ${_search_dir}/$1*.zip 2>/dev/null | wc -l` - - # search tar file -# tar_count=`find ${_search_dir} -maxdepth 1 -name "$1*.tar.*" | wc -l` - tar_count=`ls ${_search_dir}/$1*.tar.* 2>/dev/null | wc -l` - - # duplicate file check - if [ 1 -lt `expr $zip_count + $tar_count` ]; then - echo "file1_zip = $zip_count" - echo "file1_tar = $tar_count" - func_error "ERROR: $1: too many files" - fi - - crypto_zip_count=0 - for i in ${_crypto_pkg_list} - do - if [ $1 = $i ]; then - crypto_zip_count=$zip_count - zip_count=0 - fi - done - - # set result - if [ 1 = $zip_count ]; then - _find_filename=$(ls ${_search_dir}/$1*.zip) - _extract_mode=${_MODE_ZIP} - elif [ 1 = $tar_count ]; then - _find_filename=$(ls ${_search_dir}/$1*.tar.*) - _extract_mode=${_MODE_TAR} - elif [ 1 = $crypto_zip_count ]; then - _find_filename=$(ls ${_search_dir}/$1*.zip) - _extract_mode=${_MODE_CRYPTO_ZIP} - else - _find_filename="" - fi -} - -# $1: Mode -# $2: archive file name -func_cmn_extract_archive() -{ - case $1 in - $_MODE_ZIP) -# echo "Zip mode" - unzip -oq $2 - ;; - $_MODE_TAR) -# echo "Tar mode" - tar xf $2 - ;; - $_MODE_CRYPTO_ZIP) -# echo "Crypto Zip mode" - unzip -oq $2 - top_dir=$(basename $2) - top_dir=${top_dir%.*} - cd ${top_dir} - unzip -oq *.zip - if [ $? -gt 0 ]; then - func_error "ERROR: FAILED ZIP PASSWORD" - fi - cd ${TMPWORK} - ;; - *) - func_error "ERROR: func_cmn_extract_archive: mode error." - exit 1 - ;; - esac -} - -# $1: set target filename. -# $2: set MD5 expectation value. -func_cmn_md5_check() -{ - _md5_func_param_filename=$1 - _md5_func_param_expectation=$2 - if [ ! -e ${_md5_func_param_filename} ]; then - func_error "func_cmn_md5_check : ERROR ${_md5_func_param_filename} not found." - fi - - _calc_md5=$(md5sum ${_md5_func_param_filename} | cut -d " " -f1) - - if [ -n "${_no_md5check}" ] || [ -z ${_md5_func_param_expectation} ]; then - echo "Skip MD5 : `basename ${_md5_func_param_filename}`" - return - fi - - if [ -n "${_debug}" ]; then - echo "MD5 target file = ${_md5_func_param_filename}" - echo "calc_md5 = ${_calc_md5}" - echo "expect_value = ${_md5_func_param_expectation}" - fi - - if [ ${_calc_md5} = ${_md5_func_param_expectation} ]; then - echo "MD5 OK : `basename ${_md5_func_param_filename}`" - else - echo "calc_md5 = ${_calc_md5}" - echo "expect_value = ${_md5_func_param_expectation}" - func_error "MD5 ERROR : ${_md5_func_param_filename}" - fi -} - -##### Error function -# $1: error message -func_error() -{ - echo "$1" - # cleanup temp directory. - func_clean_tempdir - exit 1 -} - -##### cleanup temp directory -func_clean_tempdir() -{ - echo "cleanup temp directory" - rm -rf ${TMPWORK} -} - -##### Template function for Single package - -# $1: package name -# $2: search target filename -# $3: search directory (full path) -# return -# _find_filename : the found file (full path) -# _extract_top_dir_name -func_search_file_in_package() -{ - # search package file - func_cmn_find_file $1 $3 - if [ -n "${_debug}" ]; then - echo "" - echo "FileName = ${_find_filename}" - echo "Mode = ${_extract_mode}" - fi - - if [ -z "${_find_filename}" ]; then - return - fi - - # extract - func_cmn_extract_archive ${_extract_mode} "${_find_filename}" - - # Get directory name - # {PATH}/Package_Version.tar.gz or XXXX.zip --> Package_Version - top_dir=$(basename ${_find_filename}) - top_dir=${top_dir%.*} - - # search file - num=`find ${top_dir} -name $2 | wc -l` - if [ ${num} -eq 1 ]; then - _find_filename=`find ${top_dir} -name $2` - else - # same filename exists. - _find_filename=`find ${top_dir} -name $2 | grep Software` - fi - - # set mode - if [ `echo ${_find_filename} | grep '\.'zip` ]; then - _extract_mode=${_MODE_ZIP} - else - _extract_mode=${_MODE_TAR} - fi - - # set return value - _extract_top_dir_name=${top_dir} -} - -# $1: package name -# $2: copy filename (md5 target) -# $3: expect MD5 value -# $4: search directory (full path) -# return -# _find_file_name -# _extract_top_dir_name -func_search_and_md5check() -{ - # search package file - func_cmn_find_file $1 $4 - if [ -n "${_debug}" ]; then - echo "" - echo "FileName = ${_find_filename}" - echo "Mode = ${_extract_mode}" - fi - - if [ -z "${_find_filename}" ]; then - return - fi - - # extract - func_cmn_extract_archive ${_extract_mode} "${_find_filename}" - - # MD5 - # Get directory name - # {PATH}/Package_Version.tar.gz or XXXX.zip --> Package_Version - top_dir=$(basename ${_find_filename}) - top_dir=${top_dir%.*} - - # call func_cmn_md5_check - func_cmn_md5_check "${top_dir}/$1/Software/$2" "$3" - - # set return value - _extract_top_dir_name=${top_dir} -} - -##### Template function for Group package -# $1: group package name -# $2: single package name -# $3: copy filename (md5 target) -# $4: expect MD5 value -# $5: search directory (full path) -# return -# _find_file_name -# _extract_top_dir_name -# -# NOTE) This function supports level1 packaging. Do not support "grp pkg in grp pkg". -func_search_and_md5check_grp() -{ - # search group package @SRCDIR - func_cmn_find_file $1 $5 - if [ -n "${_debug}" ]; then - echo "search group package" - echo "FileName = ${_find_filename}" - echo "Mode = ${_extract_mode}" - echo "" - fi - - if [ -z "${_find_filename}" ]; then - return - fi - - # extract group package @TMPWORK - func_cmn_extract_archive ${_extract_mode} "${_find_filename}" - - cd ${_find_filename} - # check group pachage structure - # <Package name>_<version>/Package_Info.txt - top_dir=$(basename ${_find_filename}) - top_dir=${top_dir%.*} - - if [ ! -e ${top_dir}/Package_Info.txt ]; then - echo "grp package = $1" - echo "single package = $2" - func_error "ERROR: Package_Info.txt not found in Group package." - fi - - # search single package @TMPWORK/TOPDIR/<Group Package name>/ - func_cmn_find_file $2 "${TMPWORK}/${top_dir}/$1" - if [ -n "${_debug}" ]; then - echo "search single package" - echo "FileName = ${_find_filename}" - echo "Mode = ${_extract_mode}" - echo "" - fi - - if [ -z "${_find_filename}" ]; then - return - fi - - # mv <single package> TMPWORK/. - mv ${_find_filename} ${TMPWORK}/. - - # delete group package - rm -rf ${TMPWORK}/${top_dir} - - # call search and md5check @TMPWORK - func_search_and_md5check $2 $3 $4 ${TMPWORK} -} - -##### File search and MD5check for Package list -# $1: package list -# $2: rigid flag (1: true, other: false) -# -# return -# 1: [Success] One or more files were found. -# 0: [Fail] File not found -# -# package list format -# list ="<software_name>,<package_name>,<copy_file_name>,<md5_variable_name> \ -# <software_name>,<package_name>,<copy_file_name>,<md5_variable_name> \ -# <software_name>,<package_name>,<copy_file_name>,<md5_variable_name>" -# -# Note) Don't use space in xxx_name. -# Note) md5_variable_name is defined in md5list.txt. -# Prefix "_MD5_" is added automaticary. ex) FOO --> _MD5_FOO -# It is omissible. The default is "_MD5_<package_name>". -func_list_search_and_md5check () -{ - find_flag=0 - - for i in $1 - do - sw_name=`echo $i | cut -d "," -f 1` - pkg_name=`echo $i | cut -d "," -f 2` - copyfile_name=`echo $i | cut -d "," -f 3` - md5_val=`echo $i | cut -d "," -f 4` - - # <MD5_name> is empty. Default MD5 name is "_MD5_<pkg_name>" - if [ -z "${md5_val}" ]; then - md5_val=`eval echo '$_MD5_'${pkg_name}` - else - md5_val=`eval echo '$_MD5_'${md5_val}` - fi - - if [ -n "${_debug}" ]; then - echo "" - echo "sw_name = $sw_name" - echo "pkg_name = $pkg_name" - echo "copyfile_name = $copyfile_name" - echo "md5_val = $md5_val" - fi - - func_search_and_md5check "${pkg_name}" "${copyfile_name}" "${md5_val}" "${_src_full}" - if [ -z "${_find_filename}" ]; then - echo "${sw_name} not found!" - # rigid flag = TRUE. Not found = ERROR - if [ "X$2" = "X1" ]; then - return 0 - fi - else - find_flag=1 - fi - done - - return ${find_flag} -} - -##### File search and install (without MD5check) for Package list -# -# $1: package list -# $2: install directory -# -# return -# 1: [Success] One or more files were installed. -# 0: [Fail] File not found -# -# package list format -# list ="<software_name>,<package_name>,<copy_file_name>,<md5_variable_name> \ -# <software_name>,<package_name>,<copy_file_name>,<md5_variable_name> \ -# <software_name>,<package_name>,<copy_file_name>,<md5_variable_name>" -# -# Note) Don't use space in xxx_name. -# Note) md5_variable_name is defined in md5list.txt. -# Prefix "_MD5_" is added automaticary. ex) FOO --> _MD5_FOO -# It is omissible. The default is "_MD5_<package_name>". -func_list_search_and_install_wo_md5check() -{ - find_flag=0 - - for i in $1 - do - sw_name=`echo $i | cut -d "," -f 1` - pkg_name=`echo $i | cut -d "," -f 2` - copyfile_name=`echo $i | cut -d "," -f 3` - md5_val=`echo $i | cut -d "," -f 4` - - # <MD5_name> is empty. Default MD5 name is "_MD5_<pkg_name>" - if [ -z "${md5_val}" ]; then - md5_val=`eval echo '$_MD5_'$pkg_name` - else - md5_val=`eval echo '$_MD5_'${md5_val}` - fi - - copyfile_name=$(basename ${copyfile_name}) - - if [ -n "${_debug}" ]; then - echo "" - echo "sw_name = $sw_name" - echo "pkg_name = $pkg_name" - echo "copyfile_name = $copyfile_name" - echo "md5_val = $md5_val" - fi - - # file search - func_search_file_in_package "${pkg_name}" "${copyfile_name}" "${_src_full}" - if [ -z "${_find_filename}" ]; then - echo "${sw_name} not found!" - else - find_flag=1 - - # install - install -d $2 - install -m 0644 ${_find_filename} $2 - echo "Installed $sw_name" - echo " : ${pkg_name}" - fi - done - - return ${find_flag} -} - -##### File search and install for Package list -# -# $1: package list -# $2: install directory -# -# return -# 1: [Success] One or more files were installed. -# 0: [Fail] File not found -# -# package list format -# list ="<software_name>,<package_name>,<copy_file_name>,<md5_variable_name> \ -# <software_name>,<package_name>,<copy_file_name>,<md5_variable_name> \ -# <software_name>,<package_name>,<copy_file_name>,<md5_variable_name>" -# -# Note) Don't use space in xxx_name. -# Note) md5_variable_name is defined in md5list.txt. -# Prefix "_MD5_" is added automaticary. ex) FOO --> _MD5_FOO -# It is omissible. The default is "_MD5_<package_name>". -func_list_search_and_install() -{ - find_flag=0 - - for i in $1 - do - sw_name=`echo $i | cut -d "," -f 1` - pkg_name=`echo $i | cut -d "," -f 2` - copyfile_name=`echo $i | cut -d "," -f 3` - md5_val=`echo $i | cut -d "," -f 4` - - # <MD5_name> is empty. Default MD5 name is "_MD5_<pkg_name>" - if [ -z "${md5_val}" ]; then - md5_val=`eval echo '$_MD5_'$pkg_name` - else - md5_val=`eval echo '$_MD5_'${md5_val}` - fi - - if [ -n "${_debug}" ]; then - echo "" - echo "sw_name = $sw_name" - echo "pkg_name = $pkg_name" - echo "copyfile_name = $copyfile_name" - echo "md5_val = $md5_val" - fi - - # seach & MD5 check - func_search_and_md5check "${pkg_name}" "${copyfile_name}" "${md5_val}" "${_src_full}" - if [ -z "${_find_filename}" ]; then - echo "${sw_name} not found!" - else - find_flag=1 - - # Get directory name - # _find_filename = pkg file (full path). It is not copyfile. - top_dir=$(basename ${_find_filename}) - top_dir=${top_dir%.*} - - # install - install -d $2 - install -m 0644 ${top_dir}/${pkg_name}/Software/${copyfile_name} $2 - echo "Installed $sw_name" - echo " : ${pkg_name}" - fi - done - - return ${find_flag} -} - -##### Package function - -# For 3D graphics packages -func_gfx() -{ - echo "" - echo "Copying for Graphic Packages" - - copy_flag=0 - - for i in ${_gfx_list} - do - user_pkg_name=`echo $i | cut -d "," -f 1` - user_copyfile_name=`echo $i | cut -d "," -f 2` - user_md5_val=`eval echo '$_MD5_'${user_pkg_name}` - kern_pkg_name=`echo $i | cut -d "," -f 3` - kern_copyfile_name=`echo $i | cut -d "," -f 4` - kern_md5_val=`eval echo '$_MD5_'${kern_pkg_name}` - - if [ -n "${_debug}" ]; then - echo "" - echo "user_pkg_name = ${user_pkg_name}" - echo "user_copyfile_name= ${user_copyfile_name}" - echo "user_md5_val = ${user_md5_val}" - echo "kern_pkg_name = ${kern_pkg_name}" - echo "kern_copyfile_name= ${kern_copyfile_name}" - echo "kern_md5_val = ${kern_md5_val}" - fi - - # user module (file1) - func_search_and_md5check "${user_pkg_name}" "${user_copyfile_name}" "${user_md5_val}" "${_src_full}" - - if [ -z "${_find_filename}" ]; then - echo "${user_pkg_name} not found!" - continue - fi - - file1_top_dir=${_extract_top_dir_name} - echo "file1 top : ${file1_top_dir}" - - # kernel module (file2) - func_search_and_md5check "${kern_pkg_name}" "${kern_copyfile_name}" "${kern_md5_val}" "${_src_full}" - - # file1 exist, but file2 not exist - if [ -z "${_find_filename}" ]; then - func_error "ERROR: func_gfx: package file for Graphic is incomplete." - fi - - file2_top_dir=${_extract_top_dir_name} - echo "file2 top : ${file2_top_dir}" - - # Finally copy is performed - copy_flag=1 - install -d ${_GFX_UM_INST_DIR} - install -m 0644 ${file1_top_dir}/${user_pkg_name}/Software/${user_copyfile_name} ${_GFX_UM_INST_DIR}/${user_copyfile_name##INF_} - install -d ${_GFX_KM_INST_DIR} - install -m 0644 ${file2_top_dir}/${kern_pkg_name}/Software/${kern_copyfile_name} ${_GFX_KM_INST_DIR} - echo "Installed GFX package" - echo " : ${user_pkg_name}" - echo " : ${kern_pkg_name}" - echo "" - done - - if [ ${copy_flag} -eq 0 ]; then - return - fi - - echo "" - echo "Packages for GFX module were found and copied." - echo /=======================================================/ -} - -##### For Multi Media - -# For Audio library copy -# -# Global -# _audio_list: audio library list -# Return -# 0: Not found -# 1: Success -func_audio_lib() -{ - # MD5 check: OMX Media Component Audio Common Library for Linux - func_list_search_and_md5check "${_audio_common_list}" "1" - if [ $? -eq 0 ]; then - echo "Audio Common Library not found!" - echo "" - return 0 - fi - - # MD5 check: audio library. - func_list_search_and_md5check "${_audio_list}" - if [ $? -eq 0 ]; then - # library not found. - echo "" - echo "Audio library not found." - return 0 - fi - - # Add audio common library to list - _audio_list="${_audio_common_list} ${_audio_list}" - - # Install omx common lib (if not installed) - func_install_omx_common - - # Install Audio library packages - func_list_search_and_install_wo_md5check "${_audio_list}" "${_OMX_UM_INST_DIR}" - _audio_common_install=1 - - return 1 -} - -# For Audio library -func_audio() -{ - echo "" - echo "Copying for Audio Common Packages" - - _audio_common_install=0 - - # Audio requires OMX common library - if [ ${_omx_common_install} -eq 0 ]; then - # MD5 check (rigid flag=TRUE) - func_list_search_and_md5check "${_omx_common_list}" "1" - if [ $? -eq 0 ]; then - echo "OMX Common Library not found!" - echo "" - return - fi - else - echo "OMX Common Library already installed" - fi - - # Audio Library - func_audio_lib - if [ $? -eq 0 ]; then - echo "" - echo "Skip Audio Packages" - echo "" - return - fi - - echo "" - echo "Packages for Audio module were found and copied." - echo /=======================================================/ -} - -# For Audio M/W -# Global -# _audio_mw_list: audio M/W library list -# Return -# 0: Not found -# 1: Success -func_audio_mw() -{ - echo "" - echo "Copying for Audio M/W Packages" - - # MD5 check - func_list_search_and_md5check "${_audio_mw_list}" - if [ $? -eq 0 ]; then - # library not found. - echo "" - echo "Packages for Audio M/W module were not found." - return 0 - fi - - # Install Audio M/W library packages - func_list_search_and_install_wo_md5check "${_audio_mw_list}" "${_OMX_UM_INST_DIR}" - - echo "" - echo "Packages for Audio M/W module were found and copied." - echo /=======================================================/ - - return 1 -} - -# install OMX common library -func_install_omx_common() -{ - if [ ${_omx_common_install} -eq 0 ]; then - echo "" - echo "Install for OMX Common Packages" - func_list_search_and_install_wo_md5check "${_omx_common_list}" "${_OMX_UM_INST_DIR}" - _omx_common_install=1 - fi -} - -# install uvcs driver -func_install_uvcs() -{ - if [ ${_uvcs_install} -eq 0 ]; then - echo "" - echo "Installed UVCS driver" - func_list_search_and_install_wo_md5check "${_uvcs_list}" "${_UVCS_INST_DIR}" - _uvcs_install=1 - fi -} - -# search & MD5 check for OMX Video Decoder library -# Global -# _video_dec_list: video decoder list -# Return -# 0: Not found -# 1: Success -func_video_decoder_lib() -{ - echo "" - echo "Copying for Video Decoder Library Packages" - - # MD5 check: Decoder Common Library (rigid flag=TRUE) - func_list_search_and_md5check "${_video_dec_common_list}" "1" - if [ $? -eq 0 ]; then - echo "OMX Video Decoder Common Library not found!" - return 0 - fi - - # MD5 check: Video Decoder Library - func_list_search_and_md5check "${_video_dec_list}" - if [ $? -eq 0 ]; then - # library not found. - return 0 - fi - - # install OMX common lib (if not installed) - func_install_omx_common - - # install UVCS driver (if not installed) - func_install_uvcs - - # Add video decoder common lib to list - _video_dec_list="${_video_dec_common_list} ${_video_dec_list}" - - # install searched library - func_list_search_and_install_wo_md5check "${_video_dec_list}" "${_OMX_UM_INST_DIR}" - _video_decoder_common_install=1 - - return 1 -} - -# search & MD5 check for OMX Video Encoder library -# Global -# _video_enc_list: video encoder list -# Return -# 0: Not found -# 1: Success -func_video_encoder_lib() -{ - echo "" - echo "Copying for Video Encoder Library Packages" - - - # MD5 check Encoder Common Library (rigid flag=TRUE) - func_list_search_and_md5check "${_video_enc_common_list}" "1" - if [ $? -eq 0 ]; then - echo "OMX Video Encoder Common Library not found!" - return 0 - fi - _video_encoder_common_install=0 - - # Video Encoder Library - # MD5 check - func_list_search_and_md5check "${_video_enc_list}" - if [ $? -eq 0 ]; then - # library not found. - return 0 - fi - - # install common lib (if not installed) - func_install_omx_common - - # install UVCS driver (if not installed) - func_install_uvcs - - # Add Video encoder common library to list - _video_enc_list="${_video_enc_common_list} ${_video_enc_list}" - - # install searched library - func_list_search_and_install_wo_md5check "${_video_enc_list}" "${_OMX_UM_INST_DIR}" - _video_encoder_common_install=1 - - return 1 -} - -# For Video decoder -# Global -# _video_dec_list: video decoder list -# Return -# 0: Not found -# 1: Success -func_video_decoder() -{ - echo "" - echo "Copying for Video Decoder Packages" - - # OMX Common library - if [ ${_omx_common_install} -eq 0 ]; then - # MD5 check (rigid flag=TRUE) - func_list_search_and_md5check "${_omx_common_list}" "1" - if [ $? -eq 0 ]; then - echo "OMX Common Library not found!" - echo "" - return - fi - else - echo "OMX Common Library already installed" - fi - - # UVCS driver - if [ ${_uvcs_install} -eq 0 ]; then - # MD5 check (rigid flag=TRUE) - func_list_search_and_md5check "${_uvcs_list}" "1" - if [ $? -eq 0 ]; then - echo "UVCS driver not found!" - echo "" - return - fi - else - echo "UVCS driver already installed" - fi - - # OMX Decoder - # Decoder common Lib - func_video_decoder_lib - if [ $? -eq 0 ]; then - echo "" - echo "Skip Video Decoder Packages" - echo "" - return - fi - - echo "" - echo "Packages for video decoder module were found and copied." - echo /=======================================================/ -} - -# For Video encoder -func_video_encoder() -{ - echo "" - echo "Copying for Video Encoder Packages" - - # OMX Common library - if [ ${_omx_common_install} -eq 0 ]; then - # MD5 check (rigid flag=TRUE) - func_list_search_and_md5check "${_omx_common_list}" "1" - if [ $? -eq 0 ]; then - echo "OMX Common Library not found!" - echo "" - return - fi - else - echo "OMX Common Library already installed" - fi - - # UVCS driver - if [ ${_uvcs_install} -eq 0 ]; then - # MD5 check (rigid flag=TRUE) - func_list_search_and_md5check "${_uvcs_list}" "1" - if [ $? -eq 0 ]; then - echo "UVCS driver not found!" - echo "" - return - fi - else - echo "UVCS driver already installed" - fi - - # OMX Encoder - # Encoder common Lib - func_video_encoder_lib - if [ $? -eq 0 ]; then - echo "" - echo "Skip Video Encoder Packages" - echo "" - return - fi - - echo "" - echo "Packages for video encoder module were found and copied." - echo /=======================================================/ -} - -# For DTV kernel module -func_dtv_kern() -{ - echo "" - echo "Copying for DTV kernel module" - - _dtv_kern_install=0 - - func_list_search_and_md5check "${_dtv_km_list}" - if [ $? -eq 0 ]; then - # library not found. - echo "" - echo "DTV kernel library not found!" - return - fi - - pkg_name=`echo ${_dtv_km_list} | cut -d "," -f 2` - copyfile_name=`echo ${_dtv_km_list} | cut -d "," -f 3` - - # extract --> archive --> copied - echo "Installed DTV kernel modules" - func_search_file_in_package "${pkg_name}" "${copyfile_name}" "${_src_full}" - func_cmn_extract_archive "${_extract_mode}" "${_find_filename}" - - dtv_driver_list="ssp_drv scu_src_drv tsif_drv tddmac_drv" - for i in ${dtv_driver_list} - do - tar cfz $i.tar.gz $i - install -d ${_DTV_KM_INST_DIR} - install -m 644 $i.tar.gz ${_DTV_KM_INST_DIR} - echo " : $i.tar.gz" - done - - _dtv_kern_install=1 - - echo "" - echo "DTV kernel module were found and copied." - echo /=======================================================/ -} - -# For DTV lib -func_dtv_lib() -{ - echo "" - echo "Copying for DTV Library Packages" - - # DTV kernel modules - if [ ${_dtv_kern_install} -eq 0 ]; then - echo "DTV kernel module not found!" - echo "Skip DTV Package" - echo "" - return - fi - - # MD5 check (rigid flag=TRUE) - func_list_search_and_md5check "${_dtv_um_list}" "1" - if [ $? -eq 0 ]; then - # library not found. - echo "" - echo "DTV library not found" - return - fi - - # install - func_list_search_and_install_wo_md5check "${_dtv_um_list}" "${_DTV_UM_INST_DIR}" - - echo "" - echo "DTV Package were found and copied." - echo /=======================================================/ -} - -# For DVD lib -func_dvd_lib() -{ - echo "" - echo "Copying for DVD Library Packages" - - # MD5 check (rigid flag=TRUE) - func_list_search_and_md5check "${_dvd_list}" - if [ $? -eq 0 ]; then - # library not found. - echo "" - echo "DVD library not found" - return - fi - - index="1" - # install searched library - for i in ${_dvd_list}; do - install_dir=`echo ${_DVD_UM_INST_DIR} | cut -d " " -f ${index}` - func_list_search_and_install_wo_md5check ${i} ${install_dir} - index=`expr ${index} + 1` - done - - echo "" - echo "DVD Package were found and copied." - echo /=======================================================/ -} - -# For DTV/DVD main routine -func_dtv_dvd() -{ - echo "" - echo "Copying for DTV/DVD Packages" - - # DTV package - func_dtv_kern - func_dtv_lib - - # DVD package - func_dvd_lib -} - -# For CMS main routine -func_cms() -{ - echo "" - echo "Copying for CMS Packages" - - copy_flag=0 - - # MD5 check - func_list_search_and_md5check "${_cms_list}" - if [ $? -eq 0 ]; then - # library not found. - echo "Skip CMS package" - echo "" - return - fi - - # Install library - func_list_search_and_install_wo_md5check "${_cms_list}" "${_CMS_UM_INST_DIR}" - - echo "" - echo "Packages for CMS were found and copied." - echo /=======================================================/ -} - -# For ADSP main routine -func_adsp() -{ - echo "" - echo "Copying for ADSP Packages" - - # MD5 check (rigid flag = TRUE) - # In ADSP, all files are necesarry - func_list_search_and_md5check "${_adsp_km_list}" "1" - if [ $? -eq 0 ]; then - # library not found. - echo "Skip ADSP Package" - echo "" - return - fi - - func_list_search_and_md5check "${_adsp_um_list}" "1" - if [ $? -eq 0 ]; then - # library not found. - echo "Skip ADSP Package" - echo "" - return - fi - - # Install kernel module - func_list_search_and_install_wo_md5check "${_adsp_km_list}" "${_ADSP_KM_INST_DIR}" - - # Install user module - func_list_search_and_install_wo_md5check "${_adsp_um_list}" "${_ADSP_UM_INST_DIR}" - - echo "" - echo "Packages for ADSP were found and copied." - echo /=======================================================/ -} - -# For ICCOM main routine -func_iccom() -{ - echo "" - echo "Copying for ICCOM Packages" - - # MD5 check (rigid flag = TRUE) - # In ICCOM, all files are necesarry - func_list_search_and_md5check "${_iccom_km_list}" "1" - if [ $? -eq 0 ]; then - # library not found. - echo "Skip ICCOM Package" - echo "" - return - fi - - func_list_search_and_md5check "${_iccom_um_list}" "1" - if [ $? -eq 0 ]; then - # library not found. - echo "Skip ICCOM Package" - echo "" - return - fi - - # Install kernel module - func_list_search_and_install_wo_md5check "${_iccom_km_list}" "${_ICCOM_KM_INST_DIR}" - - # Install user module - func_list_search_and_install_wo_md5check "${_iccom_um_list}" "${_ICCOM_UM_INST_DIR}" - - echo "" - echo "Packages for ICCOM were found and copied." - echo /=======================================================/ -} - -################################ -# Copy Script Main routine -################################ -echo "Copyscript for R-Car Gen3" -echo -#### 1) Checking current directory -if [ ! -d meta-rcar-gen3 ]; then - echo "ERROR: Please extract meta-renesas and cd to it, before execute $0" - exit 1 -fi - -#### 2) Checking Arguments -if [ "X$1" = "X" ]; then - usage - exit 1 -fi - -while [ $# -gt 0 ] ; do - case "$1" in - -f|--force) - _no_md5check=1 - ;; - -d|--debug) - _debug=1 - ;; - *) - _src_dirname=$(basename $1) - _src_path=$(cd $(dirname $1) && pwd) - _src_full=${_src_path}/${_src_dirname} - ;; - esac - shift -done - -# source directory check -if [ ! -d ${_src_path}/${_src_dirname} ]; then - echo "${_src_path}/${_src_dirname} not found." - usage - exit 1 -fi - -if [ -n "${_debug}" ]; then - echo "src = ${_src_dirname}" - echo "src_path = ${_src_path}" - echo "src_full = ${_src_full}" - echo "no_md5check = ${_no_md5check}" - echo "" -fi - -##### 3) create temp directory -TMPWORK=${PWD}/CP_SCRIPT_TEMP -if [ -d ${TMPWORK} ]; then - echo "ERROR: Work directory already exist." - exit 1 -fi -install -d -m 700 ${TMPWORK} -cd ${TMPWORK} - -##### 4) copy -# initialize flag -_omx_common_install=0 -_uvcs_install=0 -_audio_common_install=0 -_video_decoder_common_install=0 -_video_encoder_common_install=0 -_dtv_kern_install=0 - -func_gfx -func_audio -func_audio_mw -func_video_decoder -func_video_encoder -func_dtv_dvd -func_cms -func_adsp -func_iccom - -##### 5) cleanup temp directory -func_clean_tempdir - -##### End -echo "Complete copying !" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/copyscript/md5list.txt b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/copyscript/md5list.txt deleted file mode 100644 index 14a9cb74..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/copyscript/md5list.txt +++ /dev/null @@ -1,64 +0,0 @@ -# GFX -_MD5_RTM0RC7795GLPG0001SL41C="" -_MD5_RCH3G001L4101ZDO="" -_MD5_RTM0RC7796GLPG0001SL41C="" -_MD5_RCM3G001L4101ZDO="" -_MD5_RTM0RC7796GLPGB001SL41C="" -_MD5_RCN3G001L4101ZDO="" -_MD5_RTM0RC7799GLPG0001SL41C="" -_MD5_RCE3G001L4101ZDO="" -_MD5_INFRTM0RC7795GLPG0001SL41C="" -_MD5_INFRTM0RC7796GLPG0001SL41C="" -_MD5_INFRTM0RC7796GLPGB001SL41C="" -_MD5_INFRTM0RC7799GLPG0001SL41C="" -# OMX AUDIO -_MD5_RTM0AC0000ADAACMZ1SL41C="" -_MD5_RTM0AC0000XAAACD30SL41C="" -_MD5_RTM0AC0000XACMND30SL41C="" -_MD5_RTM0AC0000ADAAPMZ1SL41C="" -_MD5_RTM0AC0000ADMP3MZ1SL41C="" -_MD5_RTM0AC0000ADWMAMZ1SL41C="" -_MD5_RTM0AC0000XAAAPD30SL41C="" -_MD5_RTM0AC0000XAMP3D30SL41C="" -_MD5_RTM0AC0000XAWMAD30SL41C="" -_MD5_RTM0AC0000AEAACMZ1SL41C="" -_MD5_RTM0AC0000XAAACE30SL41C="" -_MD5_RTM0AC0000XAALAD30SL41C="" -_MD5_RTM0AC0000XAFLAD30SL41C="" -_MD5_RTM0AC0000XADD5D30SL41C="" -_MD5_RTM0AC0000ADDD5MZ1SL41C="" -# OMX VIDEO -_MD5_RTM0AC0000XV263D30SL41C="" -_MD5_RTM0AC0000XV264D30SL41C="" -_MD5_RTM0AC0000XCMCTL30SL41C="" -_MD5_RCG3VUDRL4101ZDO="" -_MD5_RTM0AC0000XVCMND30SL41C="" -_MD5_RTM0AC0000XV265D30SL41C="" -_MD5_RTM0AC0000XVM2VD30SL41C="" -_MD5_RTM0AC0000XVM4VD30SL41C="" -_MD5_RTM0AC0000XVVC1D30SL41C="" -_MD5_RTM0AC0000XVCMNE30SL41C="" -_MD5_RTM0AC0000XV264E30SL41C="" -_MD5_RTM0AC0000XVDVXD30SL41C="" -_MD5_RTM0AC0000XVRLVD30SL41C="" -_MD5_RTM0AC0000XVVP8D30SL41C="" -_MD5_RTM0AC0000XVVP8E30SL41C="" -_MD5_RTM0AC0000XVVP9D30SL41C="" -# DTV/DVD -_MD5_RCG3T001L4101ZDO="" -_MD5_RTM0RC0000TE020000SL41C1="" -_MD5_RTM0RC0000TE020000SL41C2="" -_MD5_RTM0RC0000XDVDC301SL41C="" -_MD5_RTM0RC0000XDVDF301SL41C="" -# CMS -_MD5_RTM0AC0000JRCMBCV0SL41C="" -_MD5_RTM0AC0000JRCMBLC0SL41C="" -_MD5_RTM0AC0000JRCMDGV0SL41C="" -# ADSP -_MD5_RCG3AHFWN0201ZDP="" -_MD5_RCG3AHIFL4101ZDP="" -_MD5_RCG3AHPDL4101ZDO="" -# ICCOM -_MD5_RCG3ZLIDL4101ZNO1="" -_MD5_RCG3ZLIDL4101ZNO2="" -_MD5_RCG3ZLILL4101ZNO="" diff --git a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/patch/patch-for-linaro-gcc/0001-rcar-gen3-add-readme-for-building-with-Linaro-Gcc.patch b/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/patch/patch-for-linaro-gcc/0001-rcar-gen3-add-readme-for-building-with-Linaro-Gcc.patch deleted file mode 100644 index 0ca10175..00000000 --- a/bsp/meta-renesas-rcar-gen3/meta-rcar-gen3/docs/sample/patch/patch-for-linaro-gcc/0001-rcar-gen3-add-readme-for-building-with-Linaro-Gcc.patch +++ /dev/null @@ -1,186 +0,0 @@ -From a217313adcfb331634c99be786b93516d38d943a Mon Sep 17 00:00:00 2001 -From: Thuy Tran <thuy.tran.xh@rvc.renesas.com> -Date: Tue, 24 Oct 2017 14:39:24 +0700 -Subject: [PATCH] rcar-gen3: Add readme for building with Linaro Gcc - -This patch add the dependent layer information, build instructions -for using Linaro Gcc. - -Updated on Dec, 2016: -- Add H3ULCB -- Change supported branch from jethro to krogoth -- Change Maintainer information. - -Updated on Oct, 2017: -- Add M3N -- Add M3ULCB -- Add meta-optee layer - -Updated on Feb, 2018: -- Add E3 -- Add elinux.org reference - -Signed-off-by: Phong Man Tran <phong.tran.wh@rvc.renesas.com> -Signed-off-by: Thao Nguyen <thao.nguyen.yb@rvc.renesas.com> -Signed-off-by: Thuy Tran <thuy.tran.xh@rvc.renesas.com> -Signed-off-by: Takamitsu Honda <takamitsu.honda.pv@renesas.com> ---- - meta-rcar-gen3/README.linaro | 127 +++++++++++++++++++++++++++++++++++++++++++ - 1 file changed, 127 insertions(+) - create mode 100644 meta-rcar-gen3/README.linaro - -diff --git a/meta-rcar-gen3/README.linaro b/meta-rcar-gen3/README.linaro -new file mode 100644 -index 0000000..e1fe40a ---- /dev/null -+++ b/meta-rcar-gen3/README.linaro -@@ -0,0 +1,127 @@ -+meta-rcar-gen3 -+============== -+ -+This layer provides that evaluation board is mounted ARM SoCs of Renesas -+Electronics, called the R-Car Generation 3. Currently, this supports -+board and the SoCs of the following: -+ - Board: Salvator-X / SoC: R8A7795 (R-Car H3), R8A7796 (R-Car M3), R8A77965 (R-Car M3N) -+ - Board: R-Car Starter Kit premier(H3ULCB) / SoC: R8A7795 -+ - Board: R-Car Starter Kit pro(M3ULCB) / SoC: R8A7796 -+ - Board: Ebisu / SoC: R8A77990 (R-Car E3) -+ -+Patches -+======= -+ -+Please submit any patches for this layer to: takamitsu.honda.pv@renesas.com -+Please see the MAINTAINERS file for more details. -+ -+Dependencies -+============ -+ -+This layer depends on: -+ -+ URI: git://git.yoctoproject.org/poky -+ layers: meta, meta-yocto, meta-yocto-bsp -+ branch: rocko -+ -+ URI: https://git.linaro.org/openembedded/meta-linaro.git -+ layers: meta-linaro-toolchain, meta-optee -+ branch: rocko -+ -+ URI: git://git.openembedded.org/meta-openembedded -+ layers: meta-oe -+ branch: rocko -+ -+Build Instructions -+================== -+ -+The following instructions require a Poky installation (or equivalent). -+ -+Initialize a build using the 'oe-init-build-env' script in Poky. e.g.: -+ -+ $ source poky/oe-init-build-env -+ -+After that, initialized configure bblayers.conf by adding meta-rcar-gen3 layer. e.g.: -+ -+ BBLAYERS ?= " \ -+ <path to layer>/poky/meta \ -+ <path to layer>/poky/meta-yocto \ -+ <path to layer>/poky/meta-yocto-bsp \ -+ <path to layer>/meta-renesas/meta-rcar-gen3 \ -+ <path to layer>/meta-linaro/meta-linaro-toolchain \ -+ <path to layer>/meta-linaro/meta-optee \ -+ <path to layer>/meta-openembedded/meta-oe \ -+ " -+ -+To build a specific target BSP, configure the associated machine in local.conf: -+ -+ MACHINE ??= "<supported board name>" -+ -+Select the SOC -+ -+ For H3: r8a7795 -+ SOC_FAMILY = "r8a7795" -+ -+ For M3: r8a7796 -+ SOC_FAMILY = "r8a7796" -+ -+ For M3N: r8a77965 -+ SOC_FAMILY = "r8a77965" -+ -+ For E3: r8a77990 -+ SOC_FAMILY = "r8a77990" -+ Already added in machine config: ebisu.conf -+ -+Must Change the Gcc version in local.conf. -+ -+ GCCVERSION="linaro-7.2" -+ -+Configure for systemd init in local.conf: -+ -+ DISTRO_FEATURES_append = " systemd" -+ VIRTUAL-RUNTIME_init_manager = "systemd" -+Configure for ivi-shell and ivi-extension -+ -+ DISTRO_FEATURES_append = " ivi-shell" -+ -+Configure for USB 3.0 -+ -+ MACHINE_FEATURES_append = " usb3" -+ -+Enable tuning support for Capacity Aware migration Strategy (CAS) -+ -+ MACHINE_FEATURES_append = " cas" -+ -+Build the target file system image using bitbake: -+ -+ $ bitbake core-image-minimal -+ -+After completing the images for the target machine will be available in the output -+directory 'tmp/deploy/images/<supported board name>'. -+ -+Images generated: -+ * Image (generic Linux Kernel binary image file) -+ * Image-<machine name>.dtb (DTB for target machine) -+ * core-image-minimal-<machine name>.tar.bz2 (rootfs tar+bzip2) -+ * core-image-minimal-<machine name>.ext4 (rootfs ext4 format) -+ -+Build Instructions for SDK -+========================== -+This may be changed in the near feature. These instructions are tentative. -+ -+Should define the staticdev in SDK image feature for installing the static libs -+to SDK in local.conf. -+ -+ SDKIMAGE_FEATURES_append = " staticdev-pkgs" -+ -+Use bitbake -c populate_sdk for generating the toolchain SDK: -+For 64-bit target SDK (aarch64): -+ -+ $ bitbake core-image-minimal -c populate_sdk -+ -+The SDK can be found in the output directory 'tmp/deploy/sdk' -+ * poky-glibc-x86_64-core-image-minimal-aarch64-toolchain-x.x.sh -+ -+Usage of toolchain SDK: -+Install the SDK to the default: /opt/poky/x.x -+(x.x is YP version, i.e. 2.1.) -+For 64-bit target SDK: -+ -+ $ sh poky-glibc-x86_64-core-image-minimal-aarch64-toolchain-x.x.sh -+ -+For 64-bit application use environment script in /opt/poky/x.x -+ -+ $ source /opt/poky/x.x/environment-setup-aarch64-poky-linux -+ -+ULCB Information -+================ -+Refer to the following for more information of ULCB: -+ -+ http://elinux.org/R-Car -+ -+The information on building and running Yocto on R-Car Generation 3 -+========================= -+Refer to the following for more information: -+ -+ https://elinux.org/R-Car/Boards/Yocto-Gen3 --- -1.9.1 - |