From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Please review john_lee/openmoko-toolchain
Date: Mon, 22 Dec 2008 13:07:28 +0100 [thread overview]
Message-ID: <ginvu0$hg4$1@ger.gmane.org> (raw)
In-Reply-To: <20081222092936.GY2135@buddha.tw.openmoko.com>
On 22-12-08 10:29, John Lee wrote:
> Hi,
>
> meta-toolchain-openmoko.bb: add feed to toolchain
>
> By modifying the opkg config files in the toolchain, the toolchain can
> expend itself by installing packages from the repository.
>
>
> We need to do some modifications to the contents of toolchain before
> the packaging complete, so we use this variable as a hook. The
> modification is to create an opkg config file so the toolchain knows
> where to get new packages. A better way might be to install
> distro-feed-configs, but that includes several opkg config files while
> alias 'opkg-target' uses just one: opkg.conf.
Suggestions for the existing patch:
* rename OPENMOKO_URI to TOOLCHAIN_FEED_URI
* move the modify_opkg_conf () to meta-toolchain.bb
* TOOLCHAIN_FEED_URI ? = "" in meta-toolchain.bb
* TOOLCHAIN_FEED_URI =
"http://downloads.openmoko.org/repository/testing" in
meta-toolchain-openmoko.bb or better, conf/distro/openmoko.conf
That way more distributions can use it and each distro version can have
it's own SDK by setting TOOLCHAIN_FEED_URI in its distro file.
As you might have noticed /etc/opkg/arch.conf isn't in any packages (not
unlike the initial devnodes), so you have to generate it for the SDK. I
ran in to the same problem with the online image creator[1] and resorted
to manually installing the conf files: [2]
regards,
Koen
[1] http://amethyst.openembedded.net/~koen/narcissus/
[2]
http://dominion.thruhere.net/git/?p=narcissus.git;a=blob;f=README;h=4a6b5998b5c57dfe85b093e456b246f168cb8d2e;hb=HEAD
next prev parent reply other threads:[~2008-12-22 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 9:29 Please review john_lee/openmoko-toolchain John Lee
2008-12-22 12:07 ` Koen Kooi [this message]
2008-12-24 6:41 ` John Lee
2009-01-05 9:18 ` John Lee
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='ginvu0$hg4$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.