[yocto] Building on target

[Gary Thomas]

On 2014-03-12 13:11, Rick Bianchi wrote:
> usbip from /usr/src/kernel/drivers/staging/usbip

I finally managed to make this comparison.  I did this by taking my Poky/Yocto
built system for a i.MX6 system (ARM Cortex-A9) and replaced the rootfs with
one for the Gumstix Overo (linaro).  The results were nothing like yours, so
it's a bit confusing.

I actually built an entire Linux kernel - not just the one directory you mentioned.

Poky/Yocto - 37 minutes
Linaro     - 48 minutes

There is some flex in these numbers as they were on different [brand] SD cards, etc,
but I sure did not see the "5 minutes for Linaro vs 24 hours on Yocto" that you reported.

Perhaps the only thing I did differently was I added the SDK tools to my Yocto system
using these meta-packages instead of the list you used.
  packagegroup-core-sdk packagegroup-core-standalone-sdk-target

You might try that to see if it makes any difference.

n.b. part of what took me so long to get these results is I was trying to run this test
on something closer to your Overo board.  I have an older OMAP DM3730 board here that I
tried to do these same steps, but it was unstable and I could not get the Linaro based
file system to work at all.  Very strange.  In any case, I think the comparison I did get
with the i.MX6 is valid.

> On Wed, Mar 12, 2014 at 11:44 AM, Gary Thomas <gary at mlbassoc.com <mailto:gary at mlbassoc.com>> wrote:
> 
>     On 2014-03-12 10:09, Rick Bianchi wrote:
>     > I completely agree with regards to the comparison, but I have compiled the same exact source on the same target (arm) and it only took 5 minutes when running the Linaro image.
>     >
>     > To clarify, the only difference is the build, one is Linaro (took 5 minutes to compile source on the target) and the other Yocto (took almost 24 hours to compile source on the target).
> 
>     Sorry, I missed that this was on the same hardware.
> 
>     What are you building?  I'm going to try and duplicate this here
>     on hardware I have that's quite similar to your Gumstix board.
> 
>     >
>     > Is there something that I am missing?
>     >
>     >
>     > On Wed, Mar 12, 2014 at 8:28 AM, Gary Thomas <gary at mlbassoc.com <mailto:gary at mlbassoc.com> <mailto:gary at mlbassoc.com <mailto:gary at mlbassoc.com>>> wrote:
>     >
>     >     On 2014-03-12 09:15, Rick Bianchi wrote:
>     >     >
>     >     > I have the gumstix-console-image with the added packages below. When I compile on the target is take a very long time for it to complete, over 24 hours. I have compiled the same
>     >     > code on the same target, but running Linaro image, and it only takes a few minutes. Is there another recipe that I need to add to the build to speed up compiling?
>     >
>     >     Doubtful.  The reason your build on the target takes so long is merely
>     >     one of horsepower - that little ARM processor just doesn't have it, especially
>     >     if you are comparing it to a typical desktop environment.
>     >
>     >     > EXTRA_IMAGE_FEATURES += "dev-pkgs"
>     >     > IMAGE_INSTALL_append =" autoconf"
>     >     > IMAGE_INSTALL_append =" autofs"
>     >     > IMAGE_INSTALL_append =" automake"
>     >     > IMAGE_INSTALL_append =" ccache”
>     >     > IMAGE_INSTALL_append =" chkconfig"
>     >     > IMAGE_INSTALL_append =" dbus-glib"
>     >     > IMAGE_INSTALL_append =" gcc"
>     >     > IMAGE_INSTALL_append =" glib-2.0"
>     >     > IMAGE_INSTALL_append =" glib-networking"
>     >     > IMAGE_INSTALL_append =" glibmm"
>     >     > IMAGE_INSTALL_append =" packagegroup-core-buildessential"
>     >     > IMAGE_INSTALL_append =" pciutils"
>     >     > IMAGE_INSTALL_append =" pkgconfig”
>     >     > IMAGE_INSTALL_append =" python-scons"
>     >     > IMAGE_INSTALL_append =" systemd-compat-units”
>     >     > IMAGE_INSTALL_append =" sysfsutils"
>     >     > IMAGE_INSTALL_append =" tcp-wrappers"
>     >     > IMAGE_INSTALL_append =" usbutils"
>     >     > IMAGE_INSTALL_append =" util-macros"

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------