From: Joerg Eesmann <jeesmann@gmx.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: New user would like some help
Date: Thu, 17 Jun 2010 22:39:46 +0200 [thread overview]
Message-ID: <1276807186.8606.1.camel@fred.uchi.de> (raw)
In-Reply-To: <89BAD49D-B779-4C20-BBC0-F220F8C440AA@keylevel.com>
Hi,
try libsdl, nothing with the suffix -native.
The native-recipes are not cross-compiled, they will go to the staging
directory, I think.
BR
Joerg
On Thu, 2010-06-17 at 20:24 +0100, Chris Tapp wrote:
> Hi,
>
> I've recently come across Openembedded and really like what I see :-)
>
> I'm trying to use it to produce a minimal Linux image and have built
> one for 'minimal-image' using the 'minimal' distro for the 'alix'
> machine. This builds and boots in Qemu, so looks good.
>
> I now want to add some other libraries to the image so that they will
> be available by default. I've tried to do this by adding IMAGE_INSTALL
> lines in to minimal-image.bb (I'll do this properly by making a copy
> soon!). e.g.
>
> IMAGE_INSTALL = "task-boot \
> libsdl-native \
> <rest of file>
>
> This appears to do something at build time, but libsdl is not in the
> image that's produced.
>
> Is this the right way to go about this? I assume not, as, but I've had
> a look at the user manual and didn't spot anything obvious in there to
> show me what I'm doing wrong.
>
> Any help would be greatly appreciated.
>
> Chris
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2010-06-17 20:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 19:24 New user would like some help Chris Tapp
2010-06-17 20:39 ` Joerg Eesmann [this message]
2010-06-17 21:15 ` Chris Tapp
2010-06-17 21:19 ` Michael Lippautz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1276807186.8606.1.camel@fred.uchi.de \
--to=jeesmann@gmx.de \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox