From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15576] New: Cannot skip post-image script with `make prepare-sdk`
Date: Sat, 20 May 2023 17:09:54 +0000 [thread overview]
Message-ID: <bug-15576-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15576
Bug ID: 15576
Summary: Cannot skip post-image script with `make prepare-sdk`
Product: buildroot
Version: 2023.02.1
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: mscdex@mscdex.net
CC: buildroot@uclibc.org
Target Milestone: ---
Generally in my post-image scripts I perform some intensive tasks that are
strictly for the benefit of the preparation and creation of disk images or
ISOs. However, if all I want to do is to prepare an SDK, I don't need to do any
of these tasks because the SDK should just be building the toolchain, host
packages, and (in my case) generating the environment-setup script.
It would be very useful to have an official/built-in way to bypass the
post-image script (and possibly the other scripts) when doing `make
prepare-sdk` (either implicitly or explicitly).
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-05-20 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-20 17:09 bugzilla [this message]
2023-05-21 0:22 ` [Buildroot] [Bug 15576] Cannot skip post-image script with `make prepare-sdk` bugzilla
2023-05-21 14:13 ` bugzilla
2023-05-22 18:24 ` bugzilla
2023-05-24 20:11 ` bugzilla
2024-06-15 15:08 ` bugzilla
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-15576-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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