From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11836] New: Embedded Shell Scripts in BusyBox
Date: Fri, 03 May 2019 14:43:33 +0000 [thread overview]
Message-ID: <bug-11836-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11836
Bug ID: 11836
Summary: Embedded Shell Scripts in BusyBox
Product: buildroot
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: br-max at re-gister.com
CC: buildroot at uclibc.org
Target Milestone: ---
BusyBox has the feature to embed custom shell scripts into the main binary
during the build process.
Details are described at the following link:
https://git.busybox.net/busybox/tree/docs/embedded-scripts.txt
If the BusyBox config FEATURE_SH_EMBEDDED_SCRIPTS is set to yes (which is the
default setting), all scripts from the 'embed' directory of the BusyBox build
folder are compressed and embedded in the BusyBox binary.
It would be great to be able to use this feature with buildroot, but (please
correct me if I'm wrong) unfortunately there is no configuration option in
buildroot to add custom scripts to the 'embed' directory of the BusyBox build
folder.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-05-03 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 14:43 bugzilla at busybox.net [this message]
2019-05-03 15:09 ` [Buildroot] [Bug 11836] Embedded Shell Scripts in BusyBox bugzilla at busybox.net
2019-05-03 18:30 ` bugzilla at busybox.net
2019-05-03 18:44 ` 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-11836-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox