From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: GPE Application Development Questions
Date: Thu, 04 Jun 2009 21:44:37 -0400 [thread overview]
Message-ID: <20090605014437.GA3406@denix.org> (raw)
In-Reply-To: <loom.20090604T233316-304@post.gmane.org>
On Thu, Jun 04, 2009 at 11:56:15PM +0000, NBeing wrote:
> The "angstrom-2008.1-test-20090104-armv5te-linux-gnueabi-toolchain-gpe.tar.bz2"
> sets up the environment like so:
>
> export PATH=/usr/local/angstrom/arm/bin:$PATH
>
> export PKG_CONFIG_SYSROOT_DIR=/usr/local/angstrom/arm/arm-angstrom-linux-
> gnueabi
>
> export PKG_CONFIG_PATH=/usr/local/angstrom/arm/arm-angstrom-linux-
> gnueabi/usr/lib/pkgconfig
>
> export CONFIG_SITE=/usr/local/angstrom/arm/site-config
>
> alias opkg='LD_LIBRARY_PATH=/usr/local/angstrom/arm/lib
> /usr/local/angstrom/arm/bin/opkg-cl -f /usr/local/angstrom/arm/etc/opkg-
> sdk.conf -o /usr/local/angstrom/arm'
>
> alias opkg-target='LD_LIBRARY_PATH=/usr/local/angstrom/arm/lib
> /usr/local/angstrom/arm/bin/opkg-cl -f /usr/local/angstrom/arm/arm-angstrom-
> linux-gnueabi/etc/opkg.conf -o /usr/local/angstrom/arm/arm-angstrom-linux-
> gnueabi'
>
>
>
> I'm using an "angstrom-2009.X-test-XXXX" image so believe I need to build my
> own toolchain. I built the image with the latest OE and everything runs on the
> board, however, I'm unable to build the simple "gpe-hello" app. I believe the
> problem has to do with my mapping of the above paths. This is what I have,
> would someone be able to confirm, fix, give advance on what I have wrong with
> them? Or a different way/tutorial I should be following on GPE Application
> Developemnt? Basically I used the "cross" folder when I could, then staging,
> then rootfs.
>
> export PATH=${HOME}/oe/build/tmp/cross/armv5te/bin:$PATH
>
> export PKG_CONFIG_SYSROOT_DIR=${HOME}/oe/build/tmp/cross/armv5te/arm-angstrom-
> linux-gnueabi
>
> export PKG_CONFIG_PATH=${HOME}/oe/build/tmp/staging/armv5te-angstrom-linux-
> gnueabi/usr/lib/pkgconfig
>
> export CONFIG_SITE= ???? (Left Out)
>
> alias opkg='LD_LIBRARY_PATH=${HOME}/oe/build/tmp/cross/armv5te/lib
> ${HOME}/oe/build/tmp/rootfs/x11-image/usr/bin/opkg-cl -f
> ${HOME}/oe/build/tmp/staging/i686-linux/etc/opkg-sdk.conf -o
> ${HOME}/oe/build/tmp/cross/armv5te'
>
> alias opkg-target='LD_LIBRARY_PATH=${HOME}/oe/build/tmp/cross/armv5te/lib
> ${HOME}/oe/build/tmp/rootfs/x11-image/usr/bin/opkg-cl -f
> ${HOME}/oe/build/tmp/rootfs/x11-image/etc/opkg.conf -o
> ${HOME}/oe/build/tmp/cross/armv5te/arm-angstrom-linux-gnueabi'
The whole point of the toolchain/SDK is to be able to build apps
like "gpe-hello" w/o having OE around, i.e. w/o cross, staging or rootfs.
> Also while I'm here, in the deploy directory there is a "modules-2.6.28-r9-
> at91sam9261ek.tgz" file build, however, I'm unsure what I'm suppose to do with
> it? If I'm suppose to flash it to my board where would I find the address to
> flash too? Thanks
That's just a tarball with kernel modules. They should already be in your
filesystem image.
--
Denys
next prev parent reply other threads:[~2009-06-05 1:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 23:56 GPE Application Development Questions NBeing
2009-06-05 1:44 ` Denys Dmytriyenko [this message]
2009-06-10 0:49 ` NBeing
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=20090605014437.GA3406@denix.org \
--to=denis@denix.org \
--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 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.