[OE-core] why does "bitbake adt-installer" build an entire toolchain?

[Robert P. J. Day]

  possibly (well, ok, almost certainly) a silly question, but why does
running a simple:

  $ bitbake adt-installer

feel the need to create an entire cross-compile toolchain for me?

  the adt-installer recipe seems really pretty simple, as most of the
work is done in do_populate_adt() which involves only a lot of cd and
mkdir and cp and sed and so on, no obvious need for a development
environment.  and right below that, a whole bunch of regular steps are
clearly "noexec"ed away:

do_populate_adt[nostamp] = "1"
do_configure[noexec] = "1"
do_compile[noexec] = "1"
do_package[noexec] = "1"
do_package_write[noexec] = "1"
do_package_write_ipk[noexec] = "1"
do_package_write_rpm[noexec] = "1"
do_package_write_deb[noexec] = "1"
do_poplulate_sysroot[noexec] = "1"

  the only thing i noticed is that the opkg content is pulled down via
subversion, so perhaps the toolchain is needed to create
subversion-native.  but if that's the case, would adding

ASSUME_PROVIDED += "subversion-native"

avoid all that toolchain creation?  it just seems that building the
adt-installer (not running it, just building it) is (or should be) a
fairly simple process.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================