On Thursday 15 August 2013 15:38:37 Paul D. DeRocco wrote:
On Thursday 15 August 2013 13:01:54 Paul D. DeRocco wrote:
This smells like one of those situations where nuking tmp
and rebuilding will fix it, and we'll never know what was wrong. I'll let
you know if that fixes it.
If
I'm planning a patch to opkg-utils to add an option to split packages
into subdirectories in the same way as debian package feeds are often
laid out. So you'd have 'a*' in a subdirectory 'a', 'b*' in 'b', etc.
Packages beginning with 'lib' are put in 'liba', 'libb', etc as
appropriate and packages
On 2013-08-15 16:29, Gary Thomas wrote:
I tried to take my existing Poky/Yocto system (using my own $DISTRO
which is a derivative of poky) and enable systemd. I'm using today's
master:
meta = cutting-edge:ff10f72abda52315b892c64f711096772d9a4c1c
Sadly, building the simplest
Hi,
There's a bug in the bugzilla for this,
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4843 . You can also look
at a mail thread,
http://lists.openembedded.org/pipermail/openembedded-core/2013-June/080328.html
for
some more context.
If you just want to get past it you can do something
[YOCTO #4196] -- https://bugzilla.yoctoproject.org/show_bug.cgi?id=4196
The description field in the recipe was changed to match the package.
Signed-off-by: mulhern mulh...@yoctoproject.org
---
recipes-security/perl/lib-perl_0.63.bb |7 ---
1 file changed, 4 insertions(+), 3
On 8/15/13 7:20 PM, Paul D. DeRocco wrote:
From: Mark Hatle
A simple way to diagnose if your package is even in the
install list is to do
bitbake -e image, then scan the output for
PACKAGE_INSTALL. If your package
is not listed there, then something has either cleared your
configuration or you
Does anyone have, or can point me to, a good recipe for qiv that will work with
Yocto 1.3?
I found an obsolete qiv recipe via openembedded, but to update it will be
basically writing a new recipe since the source locations and dependencies have
changed.
I am open to other suggestions to meet
I am new to the Yocot. I have was able succesffuly build a poky image for a
development board. I was able to generate a adt-installer using bitbake
adt-installer command. I am able to compile a simple hello world program and
run it on the development board. I need to use Boost library in my
Hi Siva,
1st Follow the developer manual to add boost library to your image. Then do
bitbake your-image-with-boost -c populate_sdk, it'll generate a SDK
tarball for you that contains cross toolchain and the sysroot that contains
the boost library, which allows you to cross develop your user
From: Paul Eggleton
You didn't mention in your reply to Saul whether the foo
package was mentioned
in log.do_rootfs or installed_pkgs.txt files in your old
tmpdir; was it?
It's in both places. Yet NONE of the various files that were supposed to
be part of that recipe ended up in the
On 16 August 2013 15:48, Wenholz, Brian (GE Healthcare)
brian.wenh...@med.ge.com wrote:
Does anyone have, or can point me to, a good recipe for qiv that will work
with Yocto 1.3?
It isn't found on layers.openembedded.org so it's probably not in any
of the major layers. It should be too
In meta-oe/recipes-graphics/xinput-calibrator (Danny branch, currently
used by Gumstix), there's a recipe called xinput-calibrator-git.bb, which
installs a script for running a touchscreen calibration app if not already
calibrated.
In
Hi Raj,
Thanks for the suggestion, I have built the image as
core-image-base , now I got the ssh, sftp working with my image.
But some more packages I need like- gtk+, I have taken those packages using the
hob and build the image bitbake core-image-base,
But when I check that image
13 matches
Mail list logo
