Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] distro/include: Add yocto-space-optimize, disabling debugging for large components
Date: Thu, 11 Jul 2024 10:30:45 +0100	[thread overview]
Message-ID: <20240711093045.1166613-1-richard.purdie@linuxfoundation.org> (raw)

Add an include file to allow turning off the debug compiler options
for a small set of recipes to reduce build on disk footprint and
package/sstate sizes.

This is currently applied to llvm, qemu and openssl target recipes.

The llvm-staticdev package takes up around 1.3GB alone. These three
changes lead to a reduction in TMPDIR size for a world build from
240GB to 199GB, also removing some very large sstate objects.

There is more that could and should be done but this does illustrate
one way to speed up and reduce build size in a focused way whilst we
ideally look into other approaches.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 meta/conf/distro/include/yocto-space-optimize.inc | 3 +++
 1 file changed, 3 insertions(+)
 create mode 100644 meta/conf/distro/include/yocto-space-optimize.inc

diff --git a/meta/conf/distro/include/yocto-space-optimize.inc b/meta/conf/distro/include/yocto-space-optimize.inc
new file mode 100644
index 00000000000..ffc121e440a
--- /dev/null
+++ b/meta/conf/distro/include/yocto-space-optimize.inc
@@ -0,0 +1,3 @@
+DEBUG_FLAGS:remove:pn-llvm = "-g"
+DEBUG_FLAGS:remove:pn-qemu = "-g"
+DEBUG_FLAGS:remove:pn-openssl = "-g"


             reply	other threads:[~2024-07-11  9:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11  9:30 Richard Purdie [this message]
2024-07-11 12:10 ` [OE-core] [PATCH] distro/include: Add yocto-space-optimize, disabling debugging for large components Ross Burton
2024-07-11 13:35   ` Richard Purdie
2024-07-11 21:40     ` Khem Raj

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=20240711093045.1166613-1-richard.purdie@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox