From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: Building on target
Date: Wed, 12 Mar 2014 09:28:37 -0600 [thread overview]
Message-ID: <53207D25.2040309@mlbassoc.com> (raw)
In-Reply-To: <CAA7h+EpU6RVwbewuJ6r04+O2CvjPBpP1z86dpAthm4_cBrrO+Q@mail.gmail.com>
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
------------------------------------------------------------
next prev parent reply other threads:[~2014-03-12 15:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 15:15 Building on target Rick Bianchi
2014-03-12 15:28 ` Gary Thomas [this message]
2014-03-12 16:09 ` Rick Bianchi
2014-03-12 18:44 ` Gary Thomas
2014-03-12 19:11 ` Rick Bianchi
2014-03-14 14:38 ` Gary Thomas
2014-03-14 14:49 ` Rick Bianchi
2014-03-14 22:16 ` Gary Thomas
2014-03-18 17:48 ` Rick Bianchi
2014-03-18 17:49 ` Rick Bianchi
2014-03-18 17:55 ` Gary Thomas
2014-03-18 18:05 ` Rick Bianchi
2014-03-18 18:30 ` Rick Bianchi
2014-03-18 18:43 ` Gary Thomas
2014-03-18 18:57 ` Rick Bianchi
2014-03-19 16:45 ` Rick Bianchi
2014-03-19 17:02 ` Gary Thomas
2014-03-19 17:17 ` Rick Bianchi
2014-03-18 17:57 ` Paul Eggleton
2014-03-18 17:53 ` Gary Thomas
2014-03-18 18:04 ` Rick Bianchi
2014-03-12 17:37 ` Philip Balister
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=53207D25.2040309@mlbassoc.com \
--to=gary@mlbassoc.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.