From: "Minchev, Todor" <todor.minchev@intel.com>
To: "bevenson@melinkcorp.com" <bevenson@melinkcorp.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: eclipse-poky: Can't build from Eclipse, but command line build works
Date: Fri, 13 Mar 2015 08:58:57 +0000 [thread overview]
Message-ID: <1426237126.26568.19.camel@intel.com> (raw)
In-Reply-To: <BN3PR0501MB109054B33836D4B641BE0EEBBB060@BN3PR0501MB1090.namprd05.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1738 bytes --]
*snip*
> > This is a different error. There seems to be a mismatch between your
> > toolchain and rootfs. Could you please share the full name of
> >
> > my_built_image.tar.gz from
> >
> > runqemu-extract-sdk <my_built_image.tar.gz>
> > <sysroot_destination_directory>"
> >
>
> I have been able to get things to build, but not exactly in a suggested manner. I copied the entire target sysroot directory (~/poky/poky_build/tmp/sysroots/at91sam9x5ek) to the previously mentioned sysroot destination directory. I re-ran "bitbake meta-ide-support" just to ensure I had a clean copy. I then modified the SDKTARGETSYSROOT to point to my copied sysroot location. With this setup, I was able to get the project to build from Eclipse. It's working, but it's a little ugly getting there.
>
core-image-minimal builds a very small image, which doesn't have all
headers and libraries required to link even a simple binary
> So I'm assuming I'm starting at the wrong point for the sysroot to extract. What do other people do?
You have two options here:
1) Generate a standalone toolchain and sdk installer.
bitbake -c populate_sdk your_image_name
This will generate an installer script-tarball in
~/poky/poky_build/tmp/deploy/sdk/
Execute this script and follow the installation instructions. This will
extract both the toolchain and sysroot to a directory of your choice
(e.g. /opt/poky/1.6.2/).
When you configure the Yocto ADT plugin in Eclipse, select "Standalone
pre-built toolchain" before you point it to the sysroot and toolchain
directories created by the installer above.
2) Base your image on one of the development images (e.g.
core-image-minimal-dev)
Cheers,
Todor
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5229 bytes --]
next prev parent reply other threads:[~2015-03-13 9:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 13:45 eclipse-poky: Can't build from Eclipse, but command line build works Bryan Evenson
2015-03-12 11:21 ` Minchev, Todor
2015-03-12 13:43 ` Bryan Evenson
2015-03-12 17:50 ` Minchev, Todor
2015-03-12 18:15 ` Bryan Evenson
2015-03-12 20:09 ` Bryan Evenson
2015-03-13 8:58 ` Minchev, Todor [this message]
2015-03-13 11:02 ` Bryan Evenson
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=1426237126.26568.19.camel@intel.com \
--to=todor.minchev@intel.com \
--cc=bevenson@melinkcorp.com \
--cc=yocto@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 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.