<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/scripts/pstage-scanner, branch bernard</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=bernard</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=bernard'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2010-07-21T14:39:53+00:00</updated>
<entry>
<title>Enable build dir outside of the poky directory</title>
<updated>2010-07-21T14:39:53+00:00</updated>
<author>
<name>Joshua Lock</name>
<email>josh@linux.intel.com</email>
</author>
<published>2010-07-21T13:55:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=971907567cff64e74f21d349d6751dadc8c09827'/>
<id>urn:sha1:971907567cff64e74f21d349d6751dadc8c09827</id>
<content type='text'>
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
&lt;&lt;later, in a different shell&gt;&gt;
$ 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 &lt;josh@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>scripts/pstage-scanner: new script to sanity test the contents of pstage</title>
<updated>2010-04-27T15:58:43+00:00</updated>
<author>
<name>Joshua Lock</name>
<email>josh@linux.intel.com</email>
</author>
<published>2010-04-22T16:51:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=d2c6f3ef36d08ac7ac8a9deab6662f4c3b1a318c'/>
<id>urn:sha1:d2c6f3ef36d08ac7ac8a9deab6662f4c3b1a318c</id>
<content type='text'>
Currently the script will scan all packages in the pstage directory and log
packages which contain destinations outside of the native sysroot.
The script currently ignores pkgdata, stamps and deploy but does trigger the
work dir for packages with a package-split file, this may well be a false
positive.

Signed-off-by: Joshua Lock &lt;josh@linux.intel.com&gt;
</content>
</entry>
</feed>
