Digi
/
meta-digi
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

meta-digi: update config templates for yocto dora 

Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This commit is contained in:
Javier Viguera 2013-12-20 17:25:06 +01:00
parent d7cfeb0fd3
commit 07541f125d
6 changed files with 36 additions and 75 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
sdk/config/ccardimx28js/bblayers.conf.sample
View File

@ -6,9 +6,9 @@ BBPATH = "${TOPDIR}"
BBFILES ?= "" BBFILES ?= ""
BBLAYERS ?= " \ BBLAYERS ?= " \
##COREBASE##/meta \ ##OEROOT##/meta \
##COREBASE##/meta-yocto \ ##OEROOT##/meta-yocto \
##COREBASE##/meta-yocto-bsp \ ##OEROOT##/meta-yocto-bsp \
##DIGIBASE##/meta-openembedded/meta-oe \ ##DIGIBASE##/meta-openembedded/meta-oe \
##DIGIBASE##/meta-openembedded/meta-networking \ ##DIGIBASE##/meta-openembedded/meta-networking \
##DIGIBASE##/meta-openembedded/meta-webserver \ ##DIGIBASE##/meta-openembedded/meta-webserver \
@ -18,6 +18,6 @@ BBLAYERS ?= " \
##DIGIBASE##/meta-digi/meta-digi-dey \ ##DIGIBASE##/meta-digi/meta-digi-dey \
" "
BBLAYERS_NON_REMOVABLE ?= " \ BBLAYERS_NON_REMOVABLE ?= " \
##COREBASE##/meta \ ##OEROOT##/meta \
##COREBASE##/meta-yocto \ ##OEROOT##/meta-yocto \
" "

27
sdk/config/ccardimx28js/local.conf.sample
View File

@ -17,12 +17,12 @@
# These two options control how much parallelism BitBake should use. The first # These two options control how much parallelism BitBake should use. The first
# option determines how many tasks bitbake should run in parallel: # option determines how many tasks bitbake should run in parallel:
# #
#BB_NUMBER_THREADS = "4" #BB_NUMBER_THREADS ?= "4"
# #
# The second option controls how many processes make should run in parallel when # The second option controls how many processes make should run in parallel when
# running compile tasks: # running compile tasks:
# #
#PARALLEL_MAKE = "-j 4" #PARALLEL_MAKE ?= "-j 4"
# #
# For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would # For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
# be appropriate for example. # be appropriate for example.
@ -42,8 +42,9 @@
# There are also the following hardware board target machines included for # There are also the following hardware board target machines included for
# demonstration purposes: # demonstration purposes:
# #
#MACHINE ?= "atom-pc"
#MACHINE ?= "beagleboard" #MACHINE ?= "beagleboard"
#MACHINE ?= "genericx86"
#MACHINE ?= "genericx86-64"
#MACHINE ?= "mpc8315e-rdb" #MACHINE ?= "mpc8315e-rdb"
#MACHINE ?= "routerstationpro" #MACHINE ?= "routerstationpro"
# #
@ -180,23 +181,9 @@ USER_CLASSES ?= "buildstats image-mklibs image-prelink"
# #
# The build system can test booting virtual machine images under qemu (an emulator) # 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 # after any root filesystems are created and run tests against those images. To
# enable this uncomment this line # enable this uncomment this line. See classes/testimage(-auto).bbclass for
#IMAGETEST = "qemu" # further details.
# #TEST_IMAGE = "1"
# This variable controls which tests are run against virtual images if enabled
# above. The following would enable bat, boot the test case under the sanity suite
# and perform toolchain tests
#TEST_SCEN = "sanity bat sanity:boot toolchain"
#
# Because of the QEMU booting slowness issue (see bug #646 and #618), the
# autobuilder may suffer a timeout issue when running sanity tests. We introduce
# the variable TEST_SERIALIZE here to reduce the time taken by the sanity tests.
# It is set to 1 by default, which will boot the image and run cases in the same
# image without rebooting or killing the machine instance. If it is set to 0, the
# image will be copied and tested for each case, which will take longer but be
# more precise.
#TEST_SERIALIZE = "1"
# #
# Interactive shell configuration # Interactive shell configuration
# #

10
sdk/config/ccimx51js/bblayers.conf.sample
View File

@ -6,9 +6,9 @@ BBPATH = "${TOPDIR}"
BBFILES ?= "" BBFILES ?= ""
BBLAYERS ?= " \ BBLAYERS ?= " \
##COREBASE##/meta \ ##OEROOT##/meta \
##COREBASE##/meta-yocto \ ##OEROOT##/meta-yocto \
##COREBASE##/meta-yocto-bsp \ ##OEROOT##/meta-yocto-bsp \
##DIGIBASE##/meta-openembedded/meta-oe \ ##DIGIBASE##/meta-openembedded/meta-oe \
##DIGIBASE##/meta-openembedded/meta-networking \ ##DIGIBASE##/meta-openembedded/meta-networking \
##DIGIBASE##/meta-openembedded/meta-webserver \ ##DIGIBASE##/meta-openembedded/meta-webserver \
@ -18,6 +18,6 @@ BBLAYERS ?= " \
##DIGIBASE##/meta-digi/meta-digi-dey \ ##DIGIBASE##/meta-digi/meta-digi-dey \
" "
BBLAYERS_NON_REMOVABLE ?= " \ BBLAYERS_NON_REMOVABLE ?= " \
##COREBASE##/meta \ ##OEROOT##/meta \
##COREBASE##/meta-yocto \ ##OEROOT##/meta-yocto \
" "

27
sdk/config/ccimx51js/local.conf.sample
View File

@ -17,12 +17,12 @@
# These two options control how much parallelism BitBake should use. The first # These two options control how much parallelism BitBake should use. The first
# option determines how many tasks bitbake should run in parallel: # option determines how many tasks bitbake should run in parallel:
# #
#BB_NUMBER_THREADS = "4" #BB_NUMBER_THREADS ?= "4"
# #
# The second option controls how many processes make should run in parallel when # The second option controls how many processes make should run in parallel when
# running compile tasks: # running compile tasks:
# #
#PARALLEL_MAKE = "-j 4" #PARALLEL_MAKE ?= "-j 4"
# #
# For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would # For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
# be appropriate for example. # be appropriate for example.
@ -42,8 +42,9 @@
# There are also the following hardware board target machines included for # There are also the following hardware board target machines included for
# demonstration purposes: # demonstration purposes:
# #
#MACHINE ?= "atom-pc"
#MACHINE ?= "beagleboard" #MACHINE ?= "beagleboard"
#MACHINE ?= "genericx86"
#MACHINE ?= "genericx86-64"
#MACHINE ?= "mpc8315e-rdb" #MACHINE ?= "mpc8315e-rdb"
#MACHINE ?= "routerstationpro" #MACHINE ?= "routerstationpro"
# #
@ -180,23 +181,9 @@ USER_CLASSES ?= "buildstats image-mklibs image-prelink"
# #
# The build system can test booting virtual machine images under qemu (an emulator) # 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 # after any root filesystems are created and run tests against those images. To
# enable this uncomment this line # enable this uncomment this line. See classes/testimage(-auto).bbclass for
#IMAGETEST = "qemu" # further details.
# #TEST_IMAGE = "1"
# This variable controls which tests are run against virtual images if enabled
# above. The following would enable bat, boot the test case under the sanity suite
# and perform toolchain tests
#TEST_SCEN = "sanity bat sanity:boot toolchain"
#
# Because of the QEMU booting slowness issue (see bug #646 and #618), the
# autobuilder may suffer a timeout issue when running sanity tests. We introduce
# the variable TEST_SERIALIZE here to reduce the time taken by the sanity tests.
# It is set to 1 by default, which will boot the image and run cases in the same
# image without rebooting or killing the machine instance. If it is set to 0, the
# image will be copied and tested for each case, which will take longer but be
# more precise.
#TEST_SERIALIZE = "1"
# #
# Interactive shell configuration # Interactive shell configuration
# #

10
sdk/config/ccimx53js/bblayers.conf.sample
View File

@ -6,9 +6,9 @@ BBPATH = "${TOPDIR}"
BBFILES ?= "" BBFILES ?= ""
BBLAYERS ?= " \ BBLAYERS ?= " \
##COREBASE##/meta \ ##OEROOT##/meta \
##COREBASE##/meta-yocto \ ##OEROOT##/meta-yocto \
##COREBASE##/meta-yocto-bsp \ ##OEROOT##/meta-yocto-bsp \
##DIGIBASE##/meta-openembedded/meta-oe \ ##DIGIBASE##/meta-openembedded/meta-oe \
##DIGIBASE##/meta-openembedded/meta-networking \ ##DIGIBASE##/meta-openembedded/meta-networking \
##DIGIBASE##/meta-openembedded/meta-webserver \ ##DIGIBASE##/meta-openembedded/meta-webserver \
@ -18,6 +18,6 @@ BBLAYERS ?= " \
##DIGIBASE##/meta-digi/meta-digi-dey \ ##DIGIBASE##/meta-digi/meta-digi-dey \
" "
BBLAYERS_NON_REMOVABLE ?= " \ BBLAYERS_NON_REMOVABLE ?= " \
##COREBASE##/meta \ ##OEROOT##/meta \
##COREBASE##/meta-yocto \ ##OEROOT##/meta-yocto \
" "

27
sdk/config/ccimx53js/local.conf.sample
View File

@ -17,12 +17,12 @@
# These two options control how much parallelism BitBake should use. The first # These two options control how much parallelism BitBake should use. The first
# option determines how many tasks bitbake should run in parallel: # option determines how many tasks bitbake should run in parallel:
# #
#BB_NUMBER_THREADS = "4" #BB_NUMBER_THREADS ?= "4"
# #
# The second option controls how many processes make should run in parallel when # The second option controls how many processes make should run in parallel when
# running compile tasks: # running compile tasks:
# #
#PARALLEL_MAKE = "-j 4" #PARALLEL_MAKE ?= "-j 4"
# #
# For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would # For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
# be appropriate for example. # be appropriate for example.
@ -42,8 +42,9 @@
# There are also the following hardware board target machines included for # There are also the following hardware board target machines included for
# demonstration purposes: # demonstration purposes:
# #
#MACHINE ?= "atom-pc"
#MACHINE ?= "beagleboard" #MACHINE ?= "beagleboard"
#MACHINE ?= "genericx86"
#MACHINE ?= "genericx86-64"
#MACHINE ?= "mpc8315e-rdb" #MACHINE ?= "mpc8315e-rdb"
#MACHINE ?= "routerstationpro" #MACHINE ?= "routerstationpro"
# #
@ -180,23 +181,9 @@ USER_CLASSES ?= "buildstats image-mklibs image-prelink"
# #
# The build system can test booting virtual machine images under qemu (an emulator) # 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 # after any root filesystems are created and run tests against those images. To
# enable this uncomment this line # enable this uncomment this line. See classes/testimage(-auto).bbclass for
#IMAGETEST = "qemu" # further details.
# #TEST_IMAGE = "1"
# This variable controls which tests are run against virtual images if enabled
# above. The following would enable bat, boot the test case under the sanity suite
# and perform toolchain tests
#TEST_SCEN = "sanity bat sanity:boot toolchain"
#
# Because of the QEMU booting slowness issue (see bug #646 and #618), the
# autobuilder may suffer a timeout issue when running sanity tests. We introduce
# the variable TEST_SERIALIZE here to reduce the time taken by the sanity tests.
# It is set to 1 by default, which will boot the image and run cases in the same
# image without rebooting or killing the machine instance. If it is set to 0, the
# image will be copied and tested for each case, which will take longer but be
# more precise.
#TEST_SERIALIZE = "1"
# #
# Interactive shell configuration # Interactive shell configuration
# #