openembedded-core.git/meta/conf/layer.conf, branch 2011-1 Mirror of openembedded-core meta/conf/layer.conf: Remove packages/*bb from BBFILES 2011-05-11T09:21:10+00:00 Khem Raj raj.khem@gmail.com 2011-05-10T23:50:14+00:00 56bf0a3094cf0dbe0c9c088f69e1569bcf8de82f packages directory has been divided into recipes-*/ dirs Signed-off-by: Khem Raj <raj.khem@gmail.com> 
packages directory has been divided into recipes-*/ dirs

Signed-off-by: Khem Raj <raj.khem@gmail.com>
conf/layer.conf: Use .= to append to BBPATH and += for BBFILES 2011-05-09T06:56:10+00:00 Khem Raj raj.khem@gmail.com 2011-05-06T05:00:53+00:00 74c4c97cda7fbda68f8e6985eaad1c0e20998429 This helps bitbake in organising BBPATH and BBFILES with given BBFILE_PRIORITY order Signed-off-by: Khem Raj <raj.khem@gmail.com> 
This helps bitbake in organising BBPATH and BBFILES with given
BBFILE_PRIORITY order

Signed-off-by: Khem Raj <raj.khem@gmail.com>
poky-default-revisions: move the SRCREV to recipe file 2011-05-04T14:05:55+00:00 Yu Ke ke.yu@intel.com 2011-04-28T07:15:58+00:00 0a57bd226cdb8332707fa0f46fcf0b067f03701a in this case, those non poky distro can also use these recipe normally Signed-off-by: Yu Ke <ke.yu@intel.com> 
in this case, those non poky distro can also use these recipe normally

Signed-off-by: Yu Ke <ke.yu@intel.com>
Replace POKYBASE with COREBASE 2011-04-20T17:07:30+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2011-04-20T15:56:03+00:00 607a7657715f6fcba467a4e55ba64f41f4e13a15 Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Major layout change to the packages directory 2010-08-27T14:29:45+00:00 Richard Purdie rpurdie@linux.intel.com 2010-08-27T14:14:24+00:00 29d6678fd546377459ef75cf54abeef5b969b5cf Having one monolithic packages directory makes it hard to find things and is generally overwhelming. This commit splits it into several logical sections roughly based on function, recipes.txt gives more information about the classifications used. The opportunity is also used to switch from "packages" to "recipes" as used in OpenEmbedded as the term "packages" can be confusing to people and has many different meanings. Not all recipes have been classified yet, this is just a first pass at separating things out. Some packages are moved to meta-extras as they're no longer actively used or maintained. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com> 
Having one monolithic packages directory makes it hard to find things
and is generally overwhelming. This commit splits it into several
logical sections roughly based on function, recipes.txt gives more
information about the classifications used.

The opportunity is also used to switch from "packages" to "recipes"
as used in OpenEmbedded as the term "packages" can be confusing to
people and has many different meanings.

Not all recipes have been classified yet, this is just a first pass
at separating things out. Some packages are moved to meta-extras as
they're no longer actively used or maintained.

Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
meta/layer.conf: Fix PATH to use POKYBASE 2010-07-22T11:24:56+00:00 Richard Purdie rpurdie@linux.intel.com 2010-07-22T11:24:56+00:00 6d3a5ac67980d0bfb0091a5ee69449eb4f32390f Signed-off-by: Richard Purdie <rpurdie@linux.intel.com> 
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
Enable build dir outside of the poky directory 2010-07-21T14:39:53+00:00 Joshua Lock josh@linux.intel.com 2010-07-21T13:55:39+00:00 971907567cff64e74f21d349d6751dadc8c09827 You need to first set up the build directory by sourcing the poky build script, after that builds can be run in that directory so long as bitbake is in $PATH removing the need to source the init script for each build. i.e: $ . poky-init-build-env ~/my-build $ bitbake some-image <<later, in a different shell>> $ cd ~/my-build $ export PATH=/path/to/bitbake/bin:$PATH $ bitbake an-image This patch also removes use of OEROOT in recipes, etc. Signed-off-by: Joshua Lock <josh@linux.intel.com> 
You need to first set up the build directory by sourcing the poky build script,
after that builds can be run in that directory so long as bitbake is in $PATH
removing the need to source the init script for each build.

i.e:
$ . poky-init-build-env ~/my-build
$ bitbake some-image
<<later, in a different shell>>
$ cd ~/my-build
$ export PATH=/path/to/bitbake/bin:$PATH
$ bitbake an-image

This patch also removes use of OEROOT in recipes, etc.

Signed-off-by: Joshua Lock <josh@linux.intel.com>
layer.conf: Set BBPATH correctly 2010-07-20T13:20:04+00:00 Richard Purdie rpurdie@linux.intel.com 2010-07-20T13:20:04+00:00 4dc54a274d1db14e6499abf99f38057265153a15 Signed-off-by: Richard Purdie <rpurdie@linux.intel.com> 
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
test: add automation framework and sanitytest 2010-07-15T11:48:25+00:00 Jiajun Xu jiajun.xu@intel.com 2010-07-07T18:06:58+00:00 fd1d661b391dfad1edaac937a17c1165f635031a Automation test is disabled by default. User need set TESTCLASS to qemu in conf/local.conf and run bitbake command "bitbake poky-image-xxx" or "bitbake poky-image-xxx -c qemuimagetest" to trigger it. Currently only the sanity test with two testcases are added. To run the test, user need prepare a testing environment: 1) "expect" should be installed on system 2) NOPASSWD should be set for user to run bitbake Signed-off-by Jiajun Xu <jiajun.xu@intel.com> 
Automation test is disabled by default. User need set TESTCLASS
to qemu in conf/local.conf and run bitbake command "bitbake
poky-image-xxx" or "bitbake poky-image-xxx -c qemuimagetest" to
trigger it. Currently only the sanity test with two testcases are
added.

To run the test, user need prepare a testing environment:
1) "expect" should be installed on system
2) NOPASSWD should be set for user to run bitbake

Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
meta-extras: Add layer configuration 2010-03-25T11:48:44+00:00 Richard Purdie rpurdie@linux.intel.com 2010-03-25T11:48:44+00:00 4e821de9e2d0925ea5dac70402cdfb2742369a9b Signed-off-by: Richard Purdie <rpurdie@linux.intel.com> 
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>