8 files changed, 0 insertions, 375 deletions
diff --git a/meta-ivi-demo/COPYING.MIT b/meta-ivi-demo/COPYING.MIT
deleted file mode 100644
index fb950dc..0000000
--- a/meta-ivi-demo/COPYING.MIT
+++ /dev/null
@@ -1,17 +0,0 @@
-Permission is hereby granted, free of charge, to any person obtaining a copy 
-of this software and associated documentation files (the "Software"), to deal 
-in the Software without restriction, including without limitation the rights 
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 
-copies of the Software, and to permit persons to whom the Software is 
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in 
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN 
-THE SOFTWARE.
diff --git a/meta-ivi-demo/README.md b/meta-ivi-demo/README.md
deleted file mode 100644
index 3acc194..0000000
--- a/meta-ivi-demo/README.md
+++ /dev/null
@@ -1,57 +0,0 @@
-meta-ivi-demo, the meta-ivi demo layer
-======================================
-
-This layer's purpose is to provide a demo image build. The layer supports
-cross-architecture application development using QEMU emulation and a SDK.
-
-Please see the
-[MAINTAINERS](http://git.yoctoproject.org/cgit/cgit.cgi/meta-ivi/tree/MAINTAINERS)
-file for information on contacting the maintainers
-of this layer, as well as instructions for submitting patches.
-
-We welcome contributions. You can contribute code, submit patches, report bugs,
-answer questions on our mailing lists and review and edit our documentation
-and much more.
-
-Subscribe to the mailing list  
-    [here](https://lists.genivi.org/mailman/listinfo/genivi-meta-ivi).  
-View or Report bugs  
-    [here](https://bugs.genivi.org/buglist.cgi?product=meta-ivi).  
-Read or Edit the wiki  
-    [here](http://wiki.projects.genivi.org/index.php/meta-ivi).  
-For information about the Yocto Project, see the  
-    [Yocto Project website](https://www.yoctoproject.org).  
-For information about the Yocto GENIVI Baseline, see the  
-    [Yocto GENIVI Baseline website](http://projects.genivi.org/GENIVI_Baselines/meta-ivi).  
-
-Layer Dependencies
-------------------
-
-URI: git://git.yoctoproject.org/meta-ivi
-> branch:   7.0  
-> revision: 
-
-URI: git://git.openembedded.org/meta-openembedded
-> layers:   meta-oe  
-> branch:   dizzy  
-> revision: 6413cdb66acf43059f94d0076ec9b8ad6a475b35
-
-URI: git://git.yoctoproject.org/poky
-> branch:   dizzy  
-> revision: 9bef9b9dddfaa90cecea75937d97a8d96f006663
-
-Supported Machines
-------------------
-
-We do support the builds for currently the following machines:
-
-* QEMU (x86-64) - emulated machine: qemux86-64
-
-
-Miscellaneous
--------------
-
-For the QEMU machine, in order to have audio, the emulation should be done
-like:
-
-> QEMU_AUDIO_DRV=alsa runqemu ivi-image-demo qemux86-64 audio
diff --git a/meta-ivi-demo/conf/bblayers.conf.sample b/meta-ivi-demo/conf/bblayers.conf.sample
deleted file mode 100644
index 631b10d..0000000
--- a/meta-ivi-demo/conf/bblayers.conf.sample
+++ /dev/null
@@ -1,24 +0,0 @@
-# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
-# changes incompatibly
-LCONF_VERSION = "6"
-
-BBPATH = "${TOPDIR}"
-BBFILES ?= ""
-
-BBLAYERS ?= " \
-  ##OEROOT##/meta \
-  ##OEROOT##/meta-yocto \
-  ##OEROOT##/meta-yocto-bsp \
-  ##OEROOT##/../meta-ivi/meta-ivi \
-  ##OEROOT##/../meta-ivi/meta-ivi-bsp \
-  ##OEROOT##/../meta-ivi/meta-ivi-demo \
-  ##OEROOT##/../meta-openembedded/meta-oe \
-  ##OEROOT##/../meta-openembedded/meta-filesystems \
-  ##OEROOT##/../meta-qt5 \
-  ##OEROOT##/../meta-openembedded/meta-ruby \
-  "
-BBLAYERS_NON_REMOVABLE ?= " \
-  ##OEROOT##/meta \
-  ##OEROOT##/meta-yocto \
-  ##OEROOT##/../meta-ivi/meta-ivi \
-  "
diff --git a/meta-ivi-demo/conf/conf-notes.txt b/meta-ivi-demo/conf/conf-notes.txt
deleted file mode 100644
index e3f4bca..0000000
--- a/meta-ivi-demo/conf/conf-notes.txt
+++ /dev/null
@@ -1,4 +0,0 @@
-Common targets are:
-    ivi-image
-    ivi-image-demo
-
diff --git a/meta-ivi-demo/conf/layer.conf b/meta-ivi-demo/conf/layer.conf
deleted file mode 100644
index 784882c..0000000
--- a/meta-ivi-demo/conf/layer.conf
+++ /dev/null
@@ -1,17 +0,0 @@
-# We have a conf and classes directory, add to BBPATH
-BBPATH =. "${LAYERDIR}:"
-
-# We have recipes-* directories, add to BBFILES
-BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
-            ${LAYERDIR}/recipes-*/*/*.bbappend"
-
-BBFILE_COLLECTIONS += "ividemo"
-BBFILE_PATTERN_ividemo = "^${LAYERDIR}/"
-BBFILE_PRIORITY_ividemo = "7"
-
-# This should only be incremented on significant changes that will
-# cause compatibility issues with other layers
-LAYERVERSION_ividemo = "1"
-
-LAYERDEPENDS_ividemo = "ivi"
-
diff --git a/meta-ivi-demo/conf/local.conf.sample b/meta-ivi-demo/conf/local.conf.sample
deleted file mode 100644
index 0c5137c..0000000
--- a/meta-ivi-demo/conf/local.conf.sample
+++ /dev/null
@@ -1,214 +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 ?= "qemux86-64"
-
-#
-# This sets the default machine to be vexpressa9 if no other machine is selected:
-MACHINE ??= "qemux86-64"
-
-#
-# 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 GENIVI Baseline project use, at
-# least initially.
-# Ultimately when creating custom policy, people will likely end up subclassing 
-# these defaults.
-#
-DISTRO ?= "poky-ivi-systemd"
-INCOMPATIBLE_LICENSE ?= "GPLv3"
-
-#
-# 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/ADT target architecture
-#
-# This variable specifies the architecture to build SDK/ADT 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, exmap, 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
-#   - 'image-swab' to perform host system intrusion detection
-# 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.
-BB_DISKMON_DIRS = "\
-    STOPTASKS,${TMPDIR},1G,100K \
-    STOPTASKS,${DL_DIR},1G,100K \
-    STOPTASKS,${SSTATE_DIR},1G,100K \
-    ABORT,${TMPDIR},100M,1K \
-    ABORT,${DL_DIR},100M,1K \
-    ABORT,${SSTATE_DIR},100M,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. This assumes there is a
-# libsdl library available on your build system.
-#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"
diff --git a/meta-ivi-demo/recipes-demo-platform/images/ivi-image-demo-sdk.bb b/meta-ivi-demo/recipes-demo-platform/images/ivi-image-demo-sdk.bb
deleted file mode 100644
index 6845396..0000000
--- a/meta-ivi-demo/recipes-demo-platform/images/ivi-image-demo-sdk.bb
+++ /dev/null
@@ -1,24 +0,0 @@
-require ivi-image-demo.bb
-
-DESCRIPTION = "meta-ivi demo image that includes everything within \
-ivi-image-demo plus meta-toolchain, development headers and libraries to \
-form a standalone SDK."
-
-inherit populate_sdk
-
-QT5PKG = ""
-
-IMAGE_FEATURES_append = "\
-	debug-tweaks         \
-	dev-pkgs             \
-	eclipse-debug        \
-	${QT5PKG}            \
-	tools-debug          \
-	tools-profile        \
-	tools-sdk            \
-	tools-testapps       \
-	"
-
-IMAGE_INSTALL_append  = "\
-	kernel-dev           \
-	"
diff --git a/meta-ivi-demo/recipes-demo-platform/images/ivi-image-demo.bb b/meta-ivi-demo/recipes-demo-platform/images/ivi-image-demo.bb
deleted file mode 100644
index 58e85b5..0000000
--- a/meta-ivi-demo/recipes-demo-platform/images/ivi-image-demo.bb
+++ /dev/null
@@ -1,18 +0,0 @@
-# Base this image on generic IVI image
-require recipes-yocto-ivi/images/ivi-image.inc
-
-DESCRIPTION = "meta-ivi demo image"
-
-PV = "0.1+snapshot-${DATE}"
-
-IMAGE_FEATURES_append = " \
-    ssh-server-openssh    \
-    "
-
-IMAGE_INSTALL_append = " \
-    packagegroup-specific-component-p1 \
-    packagegroup-abstract-component-p1 \
-    packagegroup-placeholder-component-p1 \
-    packagegroup-specific-component-p2 \
-    packagegroup-abstract-component-p2 \
-    "