From: Daniel Kenji Morgan <daniel.kenji.morgan@gmail.com>
To: yocto@yoctoproject.org
Subject: do_package task of the kernel takes extremely long
Date: Thu, 24 Jan 2013 20:29:28 +0900 [thread overview]
Message-ID: <51011B18.2070105@gmail.com> (raw)
Hello,
I'm still fairly new to Yocto, and having some trouble with kernel
packaging taking an extremely long time.
I will try and keep details as simple as possible to explain my situation.
I am building images for the machine "imx6qsabrelite" in the
"meta-fsl-arm" BSP layer using Poky 1.3 (danny).
To make it easier to test out changes to the linux kernel source, I have
a copy of the source in a local subversion repository, which is checked
out to a local working copy.
I have created a kernel recipe to inherit "externalsrc" and set "S" to
the local working copy directory.
I have added a "configure_prepend" task to stage the build directory.
I use "bitbake core-image-minimal" to build the image.
Here is what I have found from checking the "do_package" task duration
of the kernel in the build stats:
1. Using a local working copy directory (subversion 1.6), the duration
exceeds 4000 seconds.
2. Using a local working copy directory (subversion 1.7), the duration
takes approximately 800 seconds.
3. Using the original kernel recipe which obtains the kernel source off
a Git repository from the internet, the duration takes approximately 400
seconds.
Checking the "do_package" task, it seems like all directories and
sub-directorys of the source are checked recursively in the process.
I think it's safe to say that the number of subversion administrative
directorys is affecting the "do_package" task duration.
Is there any way to make the "do_package" task ignore .svn
administrative directories?
next reply other threads:[~2013-01-24 11:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 11:29 Daniel Kenji Morgan [this message]
2013-01-24 13:16 ` do_package task of the kernel takes extremely long Bruce Ashfield
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=51011B18.2070105@gmail.com \
--to=daniel.kenji.morgan@gmail.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.