how does one use a prebuilt toolchain from the toolchain/ directory?

Robert P. J. Day

it sounds like a trivial question whose answer should be easy to
find, but surprisingly, it isn't. if a user wants to save all that
toolchain-building time and take advantage of an existing toolchain,
what to do?

the ADT user's guide *sort of* addresses that, but in a somewhat
confusing way:

first, the ADT guide, in section 2.1.2, talks about how to do this,
but only after the more complicated and involved recipe for using the
ADT installer. this strikes me as backwards -- a set of alternatives
would make sense going from simplest to most complicated. using a
prebuilt toolchain would seem to be the *first* thing that should be

next, that section 2.1.2 in the ADT guide opens reasonably by
explaining how to find and download the appropriate toolchain and
then, for no apparent reason, takes this massive sidestep in a "Note"
to ask the reader to consider using bitbake to build it instead. um
... no. in the midst of explaining something really simple, it's
totally counter-productive to suddenly ask the reader to consider
something noticeably more complex and unnecessary in the context of
the current explanation.

finally, after the Note is over, the instructions return to point
3., correctly telling the reader to unload the tarball at the root
directory, then vaguely referring to some "environment setup files"
without explaining what to do with them or when to run them or what
effect they'll have on the build process from then on. should one run
the appropriate env setup file *before* invoking oe-init-build-env?
after? does it matter?

so to clarify this issue, here's a set of questions to which i know
*some* of the answers and would like to know the rest.

1) i want to save buckets of time in my builds by using a pre-built
toolchain appropriate for my architecture. can i always use one of
the toolchains at
is there any downside to doing that? if so, what?

2) do those pre-built toolchains always need to be installed under
/opt/poky? it seems pretty obvious that they do, given that the
environment setup scripts hardcode references to /opt/poky.

3) can i install multiple toolchains at the same time? it seems so --
the common native content in the toolchains seems identical so i don't
see any issue with having two or more toolchains installed at the same

4) once i install a toolchain, how do i use it? say i install the arm
toolchain, and want to build a beagleboard image. at what point do i
source the arm toolchain environment setup file? is that all it
takes? will the bitbake build process automatically recognize what
i've done and use that toolchain?

and so on, and so on. thoughts?



Robert P. J. Day Ottawa, Ontario, CANADA


Join { to automatically receive all group messages.