* Specified toolchain directory does not contain a toolchain generated with meta-ide-support.
@ 2014-09-11 23:41 Nemicolopterus Crypticus
2014-09-11 23:58 ` Bob Cochran
2014-09-12 16:57 ` Nemicolopterus Crypticus
0 siblings, 2 replies; 6+ messages in thread
From: Nemicolopterus Crypticus @ 2014-09-11 23:41 UTC (permalink / raw)
To: yocto@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]
I'm trying to set up the development environment following these
instructions:http://www.yoctoproject.org/docs/1.6/adt-manual/adt-manual.html#adt-prepare
I'm currently trying to use a toolchain from within the Build
directory, so I'm following these instructions:
http://www.yoctoproject.org/docs/1.6/adt-manual/adt-manual.html#using-the-toolchain-from-within-the-build-tree
I sourced the build environment script, and set MACHINE correctly,
then I did bitbake meta-ide-support.
But in Eclipse, when I try to point to the toolchain, I'm seeing this
error: Specified toolchain directory does not contain a toolchain
generated with "bitbake meta-ide-support".
I can see from this post
<https://www.mail-archive.com/yocto%40yoctoproject.org/msg11821.html>,
that this means Poky.Env.Script.Nonexist is true:
+Poky.Env.Script.Nonexist = Specified toolchain directory does not contain a
toolchain generated with meta-ide-support.
But the scripts appears to be there. Here are the contents of my
build/tmp directory:
/oe-core/build/tmp-eglibc$ ls
abi_version cache deploy
*environment-setup-cortexa8hf-vfp-neon-linux-gnueabi* log qa.log
saved_tmpdir sstate-control stamps sysroots work
Any pointers?
[-- Attachment #2: Type: text/html, Size: 5024 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Specified toolchain directory does not contain a toolchain generated with meta-ide-support.
2014-09-11 23:41 Specified toolchain directory does not contain a toolchain generated with meta-ide-support Nemicolopterus Crypticus
@ 2014-09-11 23:58 ` Bob Cochran
2014-09-12 16:57 ` Nemicolopterus Crypticus
1 sibling, 0 replies; 6+ messages in thread
From: Bob Cochran @ 2014-09-11 23:58 UTC (permalink / raw)
To: yocto
On 09/11/2014 07:41 PM, Nemicolopterus Crypticus wrote:
> I'm trying to set up the development environment following these instructions:
> http://www.yoctoproject.org/docs/1.6/adt-manual/adt-manual.html#adt-prepare
>
>
> I'm currently trying to use a toolchain from within the Build directory, so I'm following these instructions:
>
> http://www.yoctoproject.org/docs/1.6/adt-manual/adt-manual.html#using-the-toolchain-from-within-the-build-tree
>
>
> I sourced the build environment script, and set MACHINE correctly, then I didbitbake meta-ide-support.
>
>
> But in Eclipse, when I try to point to the toolchain, I'm seeing this error:Specified toolchain directory does not contain a toolchain generated with "bitbake meta-ide-support".
>
>
>
> I can see fromthis post <https://www.mail-archive.com/yocto%40yoctoproject.org/msg11821.html>, that this means Poky.Env.Script.Nonexist is true:
>
>
> +Poky.Env.Script.Nonexist = Specified toolchain directory does not contain a
> toolchain generated with meta-ide-support.
>
>
> But the scripts appears to be there. Here are the contents of my build/tmp directory:
>
> /oe-core/build/tmp-eglibc$ ls
> abi_version cache deploy*environment-setup-cortexa8hf-vfp-neon-linux-gnueabi* log qa.log saved_tmpdir sstate-control stamps sysroots work
>
>
> Any pointers?
Just double checking that you are specifying the "toolchain root
location" as your top level build directory (the one above
/conf/local.conf - the directory where you run bitbake).
I'm just wondering since I think the label for this field is somewhat
misleading.
Otherwise, on the surface it seems that you have what you need.
Bob
>
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Specified toolchain directory does not contain a toolchain generated with meta-ide-support.
2014-09-11 23:41 Specified toolchain directory does not contain a toolchain generated with meta-ide-support Nemicolopterus Crypticus
2014-09-11 23:58 ` Bob Cochran
@ 2014-09-12 16:57 ` Nemicolopterus Crypticus
2014-09-12 19:24 ` Bob Cochran
1 sibling, 1 reply; 6+ messages in thread
From: Nemicolopterus Crypticus @ 2014-09-12 16:57 UTC (permalink / raw)
To: yocto, yocto@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]
>Just double checking that you are specifying the "toolchain root location"
as your top level build directory (the one above /conf/local.conf - the
directory where you run bitbake).
Yes that occurred to me too, since the phrasing is a bit unclear. I tried
both. Here's a depiction of my directory structure:
oe-core
|---- build
|---- conf (including local.conf)
|---- downloads
|---- tmp-eglibc
|---- environment-setup-blahblah
|---- <etc.>
|---- <etcc>
|---- bitbake
|---- gcc-toolchain
|---- meta
|---- <etc. lots more>
I tried with the root at build, and in build/tmp-eglibc with no luck.
Is it possible the toolchain didn't get built? I'm just wondering since
that's what the error claims. Is there any way to confirm that the
toolchain did indeed get built? I ran bitbake meta-ide-toolchain, but our
system is large and I'm not familiar with every aspect of it. Is it
possible some other settings elsewhere got changed in a way that would
prevent the toolchain from building?
[-- Attachment #2: Type: text/html, Size: 2201 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Specified toolchain directory does not contain a toolchain generated with meta-ide-support.
2014-09-12 16:57 ` Nemicolopterus Crypticus
@ 2014-09-12 19:24 ` Bob Cochran
2014-09-13 0:57 ` Nemicolopterus Crypticus
0 siblings, 1 reply; 6+ messages in thread
From: Bob Cochran @ 2014-09-12 19:24 UTC (permalink / raw)
To: Nemicolopterus Crypticus, yocto@yoctoproject.org
On 09/12/2014 12:57 PM, Nemicolopterus Crypticus wrote:
> >Just double checking that you are specifying the "toolchain root
> location" as your top level build directory (the one above
> /conf/local.conf - the directory where you run bitbake).
>
> Yes that occurred to me too, since the phrasing is a bit unclear. I
> tried both. Here's a depiction of my directory structure:
>
> oe-core
> |---- build
> |---- conf (including local.conf)
> |---- downloads
> |---- tmp-eglibc
> |---- environment-setup-blahblah
> |---- <etc.>
> |---- <etcc>
> |---- bitbake
> |---- gcc-toolchain
> |---- meta
> |---- <etc. lots more>
>
> I tried with the root at build, and in build/tmp-eglibc with no luck.
>
> Is it possible the toolchain didn't get built?
What happens when you source your environment script? You should have
your path set up to find your cross toolchain. If that's the case, you
should be able to run the toolchain on the command line.
I work with the powerpc toolchain, so I can cross-compile a simple test
app after sourcing my env script:
powerpc64-poky-linux-gcc main.c -o tst
and verify I have generated a 64-bit powerpc ELF executable with
file tst
I'm just wondering since
> that's what the error claims. Is there any way to confirm that the
> toolchain did indeed get built? I ran bitbake meta-ide-toolchain, but
> our system is large and I'm not familiar with every aspect of it. Is it
> possible some other settings elsewhere got changed in a way that would
> prevent the toolchain from building?
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Specified toolchain directory does not contain a toolchain generated with meta-ide-support.
2014-09-12 19:24 ` Bob Cochran
@ 2014-09-13 0:57 ` Nemicolopterus Crypticus
[not found] ` <5413C4C4.7070005@mindchasers.com>
0 siblings, 1 reply; 6+ messages in thread
From: Nemicolopterus Crypticus @ 2014-09-13 0:57 UTC (permalink / raw)
To: Bob Cochran; +Cc: yocto@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 2361 bytes --]
Yes - I can source the script, and I do successfully get my path updated.
That's unfortunate. I can run the toolchain on the command line, but the
developers I am working with need to use Eclipse. The plug-in seems like
the right solution, so I would very much like to get this to work.
It occurred to me that these issues might be because I'm using an older
version of bitbake:
$ bitbake --version
BitBake Build Tool Core version 1.20.0, bitbake version 1.20.0
Could that have something to do with the failure?
On Fri, Sep 12, 2014 at 12:24 PM, Bob Cochran <yocto@mindchasers.com> wrote:
> On 09/12/2014 12:57 PM, Nemicolopterus Crypticus wrote:
>
>> >Just double checking that you are specifying the "toolchain root
>> location" as your top level build directory (the one above
>> /conf/local.conf - the directory where you run bitbake).
>>
>> Yes that occurred to me too, since the phrasing is a bit unclear. I
>> tried both. Here's a depiction of my directory structure:
>>
>> oe-core
>> |---- build
>> |---- conf (including local.conf)
>> |---- downloads
>> |---- tmp-eglibc
>> |---- environment-setup-blahblah
>> |---- <etc.>
>> |---- <etcc>
>> |---- bitbake
>> |---- gcc-toolchain
>> |---- meta
>> |---- <etc. lots more>
>>
>> I tried with the root at build, and in build/tmp-eglibc with no luck.
>>
>> Is it possible the toolchain didn't get built?
>>
>
> What happens when you source your environment script? You should have
> your path set up to find your cross toolchain. If that's the case, you
> should be able to run the toolchain on the command line.
>
> I work with the powerpc toolchain, so I can cross-compile a simple test
> app after sourcing my env script:
>
> powerpc64-poky-linux-gcc main.c -o tst
>
> and verify I have generated a 64-bit powerpc ELF executable with
>
> file tst
>
>
>
>
>
> I'm just wondering since
>
>> that's what the error claims. Is there any way to confirm that the
>> toolchain did indeed get built? I ran bitbake meta-ide-toolchain, but
>> our system is large and I'm not familiar with every aspect of it. Is it
>> possible some other settings elsewhere got changed in a way that would
>> prevent the toolchain from building?
>>
>
>
[-- Attachment #2: Type: text/html, Size: 3199 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Specified toolchain directory does not contain a toolchain generated with meta-ide-support.
[not found] ` <5413C4C4.7070005@mindchasers.com>
@ 2014-09-23 16:10 ` Nemicolopterus Crypticus
0 siblings, 0 replies; 6+ messages in thread
From: Nemicolopterus Crypticus @ 2014-09-23 16:10 UTC (permalink / raw)
To: Bob Cochran, yocto@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 4182 bytes --]
Ok, after much strife, here's what I've gotten working. I installed the
Plugin via "Install New Software" through Eclipse:
1. While configuring the ADT Plugin for Eclipse, instead of "Build system
derived toolchain" I select "Standalone Pre-Built Toolchain."
2. Instead of BUILD as the top directory, I use build/tmp (the location of
the environment-setup script that gets created with bitbake
meta-ide-support)
3. Open Eclipse in a shell where I've already sourced that
environment-setup script <-- not sure if that's actually necessary.
Thanks to everyone for their help.. hope this helps someone else!
On Fri, Sep 12, 2014 at 9:15 PM, Bob Cochran <yocto@mindchasers.com> wrote:
> I hope one of the Intel ADT developers will jump in to help you out.
>
> Here are a few other long shots (things that I'm doing, and it works good
> for me):
>
> i) Make sure you set your environment before you start eclipse. In other
> words, invoke eclipse from a shell with the proper paths set up.
>
> ii) Use at least Poky 1.6 (I'm currently using master with success).
>
> iii) Use the pre-built plugin
>
>
> There's also an ADT installer script, but I have never tried it. I do
> everything working from git & build everything from scratch (except the
> Yocto ADT Eclipse plugin).
>
> Good luck!
>
> Bob
>
>
>
>
>
> On 09/12/2014 08:57 PM, Nemicolopterus Crypticus wrote:
>
>> Yes - I can source the script, and I do successfully get my path
>> updated. That's unfortunate. I can run the toolchain on the command
>> line, but the developers I am working with need to use Eclipse. The
>> plug-in seems like the right solution, so I would very much like to get
>> this to work.
>>
>> It occurred to me that these issues might be because I'm using an older
>> version of bitbake:
>> $ bitbake --version
>> BitBake Build Tool Core version 1.20.0, bitbake version 1.20.0
>>
>> Could that have something to do with the failure?
>>
>> On Fri, Sep 12, 2014 at 12:24 PM, Bob Cochran <yocto@mindchasers.com
>> <mailto:yocto@mindchasers.com>> wrote:
>>
>> On 09/12/2014 12:57 PM, Nemicolopterus Crypticus wrote:
>>
>> >Just double checking that you are specifying the "toolchain
>> root
>> location" as your top level build directory (the one above
>> /conf/local.conf - the directory where you run bitbake).
>>
>> Yes that occurred to me too, since the phrasing is a bit unclear.
>> I
>> tried both. Here's a depiction of my directory structure:
>>
>> oe-core
>> |---- build
>> |---- conf (including local.conf)
>> |---- downloads
>> |---- tmp-eglibc
>> |---- environment-setup-blahblah
>> |---- <etc.>
>> |---- <etcc>
>> |---- bitbake
>> |---- gcc-toolchain
>> |---- meta
>> |---- <etc. lots more>
>>
>> I tried with the root at build, and in build/tmp-eglibc with no
>> luck.
>>
>> Is it possible the toolchain didn't get built?
>>
>>
>> What happens when you source your environment script? You should
>> have your path set up to find your cross toolchain. If that's the
>> case, you should be able to run the toolchain on the command line.
>>
>> I work with the powerpc toolchain, so I can cross-compile a simple
>> test app after sourcing my env script:
>>
>> powerpc64-poky-linux-gcc main.c -o tst
>>
>> and verify I have generated a 64-bit powerpc ELF executable with
>>
>> file tst
>>
>>
>>
>>
>>
>> I'm just wondering since
>>
>> that's what the error claims. Is there any way to confirm that the
>> toolchain did indeed get built? I ran bitbake
>> meta-ide-toolchain, but
>> our system is large and I'm not familiar with every aspect of
>> it. Is it
>> possible some other settings elsewhere got changed in a way that
>> would
>> prevent the toolchain from building?
>>
>>
>>
>>
>
[-- Attachment #2: Type: text/html, Size: 5383 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-09-23 16:10 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-09-11 23:41 Specified toolchain directory does not contain a toolchain generated with meta-ide-support Nemicolopterus Crypticus
2014-09-11 23:58 ` Bob Cochran
2014-09-12 16:57 ` Nemicolopterus Crypticus
2014-09-12 19:24 ` Bob Cochran
2014-09-13 0:57 ` Nemicolopterus Crypticus
[not found] ` <5413C4C4.7070005@mindchasers.com>
2014-09-23 16:10 ` Nemicolopterus Crypticus
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.