From: Gary Thomas <gary@mlbassoc.com>
To: Joshua Lock <josh@openedhand.com>
Cc: poky@yoctoproject.org
Subject: Re: Extending SDK
Date: Wed, 24 Nov 2010 09:03:03 -0700 [thread overview]
Message-ID: <4CED3737.70900@mlbassoc.com> (raw)
In-Reply-To: <1290614009.2799.19.camel@scimitar>
On 11/24/2010 08:53 AM, Joshua Lock wrote:
> On Wed, 2010-11-24 at 08:22 -0700, Gary Thomas wrote:
>> I've built meta-toolchain-sdk and although it was saved in the
>> wrong place, all seems to be working well. Until I tried to
>> build a program that uses some package which was not part of
>> the "default" set. In particular, I tried to build 'xeyes'
>> outside of Poky using the SDK, but it needs xt and xmu libraries
>> which are built for my target, but weren't in the SDK I built.
>>
>> Questions:
>> * Did I miss something in building the SDK that left these out?
>> * Is there a way, hopefully straight forward, of adding additonal
>> packages to the SDK? Can this be done incrementally, i.e. I
>> already have an SDK installed, can I do some magic to just add
>> the xt support?
>>
>
> The SDK currently installs a fixed set of packages, the headers deemed
> useful for gnome-mobile development - this isn't currently very useful
> and is an area I'd like to improve.
>
> The SDK does come with a package manager (opkg-cl) which you should be
> able to configure to point at your existing feeds and then use to
> install additional headers into your SDK.
Thanks, I'll give it a try. I suppose that I'd need to install the -dev
packages for the stuff I want?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2010-11-24 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 15:22 Extending SDK Gary Thomas
2010-11-24 15:53 ` Joshua Lock
2010-11-24 16:03 ` Gary Thomas [this message]
2010-11-24 16:06 ` Joshua Lock
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=4CED3737.70900@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=josh@openedhand.com \
--cc=poky@yoctoproject.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