All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10386] New: Add an option to put all compiled executables that show up on target/ in staging/ as well
Date: Sun, 08 Oct 2017 17:08:27 +0000	[thread overview]
Message-ID: <bug-10386-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=10386

            Bug ID: 10386
           Summary: Add an option to put all compiled executables that
                    show up on target/ in staging/ as well
           Product: buildroot
           Version: 2017.08
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: ciro.santilli at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

Why this would be cool: you can then easily find the non-stripped executables
to debug them with gdbserver, as they are in the same relative path as in the
target.

Without that, you need to do a `find` inside build/

This is already done for shared libraries, where it is required for
compilation, and that is already great as it allows me to `set sysroot
${buildroot_out_dir}/staging`

This is an example of the type of setup I'm using:
https://github.com/cirosantilli/linux-kernel-module-cheat/tree/b89ba9b799480e4eb1975f0a704409efb7d667d1#gdbserver

Maybe we could hardlink them or something to reduce disk usage if that is a
concern.

I know that this is already doable on a per package basis, possiby by modifying
the .mk of packages, e.g. as `pciutils` has for `lspci`:

        define PCIUTILS_INSTALL_STAGING_CMDS
            $(TARGET_MAKE_ENV) $(MAKE1) -C $(@D) $(PCIUTILS_MAKE_OPTS) \
                PREFIX=$(STAGING_DIR)/usr SBINDIR=$(STAGING_DIR)/usr/bin \
                install install-lib install-pcilib
        endef

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2017-10-08 17:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-08 17:08 bugzilla at busybox.net [this message]
2019-09-30 11:14 ` [Buildroot] [Bug 10386] Add an option to put all compiled executables that show up on target/ in staging/ as well bugzilla at busybox.net
2020-04-13 23:51 ` bugzilla at busybox.net

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=bug-10386-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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.