distro_tracking: chaning owner of python-pygtk
As the python-pygtk's version is tightly connected to the gtk+ recipe version.
changing the recipe ower to Edwin who is the gtk+ recipe owner.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
This reverts commit 06570b84e4.
These versions of gst-plugins-* already have been fixed upstream
for the make 3.82 problems, so this patch detects already applied
and bails
Signed-off-by: Saul Wold <sgw@linux.intel.com>
distro_tracking: chaning owner of python-pygtk
As the python-pygtk's version is tightly connected to the gtk+ recipe version.
changing the recipe ower to Edwin who is the gtk+ recipe owner.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Cover the basics of flashing images to physical media for the Atom PC MACHINE,
as well as dealing with BIOSs that can only boot USB media in USB-ZIP mode.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
This commit patch recipe based on latest upstream code. This is GPLv3
code based. Hence the earlier patch-2.5.9 recipe is left intact for
GPLv2 needs.
Patches from 2.5.9 patch recipe are rebased to this new recipe except
these exceptions:
unified-reject-files.diff: dropped
This patch implements this new parameter:
" --unified-reject-files Create unified reject files."
And upstream has implemented very similar parameter like this:
" --reject-format=FORMAT Create 'context' or 'unified' rejects."
Hence this patch is dropped for the 2.6.1 recipe.
global-reject-file.diff: rebased
This patch is rebased to the newer upstream codebase.
install.patch: dropped
Newer upstream code now includes code form this patch.
debian.patch: dropped
This huge (10k lines) patch was specific for 2.5.9 version of GPLv2 patch.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Earlier the recipe was using 2.5.4 tar ball and a patch for upgrading to
2.5.9. Replaces these with pointer to 2.5.9 tarball.
Also noted that both 2.5.4 & 2.5.9 are GPLv2 sources.
Updated checksums and license of the recipe
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Derived the recipe from openembedded.
For poky, we use the ffmpeg lib contained in the package, while
openembedded use the system ffmpeg library.
Removed the PATH_prepend since the latest version of gst-ffmpeg
install program will be called with "-s" unless expilcitly with
"make install-strip".
Update recipe metadata.
Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
In order to support qemu user's flexibility requirement, we add extra
parameter options, user can add extra params such as "<-m 256>"
in poky-qemu script command.
Signed-off-by: Liping ke <liping.ke@intel.com>
Exclude the DATETIME variable from the KERNEL_IMAGE_BASE_NAME variable.
This avoids the last road block linux-yocto for sstate.
Signed-off-by: Kevin Tian <kevin.tian@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [BUGID: 594]
In imagetest-qemu.bbclass, we depend on DISPLAY to start qemu in
a X desktop. When user wants to run qemu sanity test, we need to
check if the variable is set.
Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
If someone has changed TMPDIR in local.conf to a non-standard location, the
poky-qemu script currently doesn't handle this and assumes if BUILDDIR is set,
$BUILDDIR/tmp will exist.
Its simple to check if this exists and if not, to ask bitbake where the
directory is so this patch changes the code to do that.
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
sstate hash validation is done at initialization of RunQueueExecuteScenequeue.
However the index of 'valid' list returned from the validation doesn't
correspond to setscene task ID. It's just an intermediate namespace between
runqueue and sstate hash func. Use it as setscene task ID fully mess the flow.
Previously this doesn't cause trouble because all setscene tasks are passed. Commit
58396a5d24 add 'noexec' concept to setscene
tasks which grabs some tasks out of the list and thus trigger this problem
Without this fix there're ~50 recipes (gzip-native, glib, ...) rebuilt weirdly
with a minimal build, even though existing sstate packages could accelerate them.
there's another typo using wrong task ID in a debug message which further hide
this issue
Signed-off-by: Kevin Tian <kevin.tian@intel.com>
