From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11986] New: Document TARGET_ variables
Date: Wed, 26 Jun 2019 12:00:56 +0000 [thread overview]
Message-ID: <bug-11986-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11986
Bug ID: 11986
Summary: Document TARGET_ variables
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: xonqnoppp at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
It is really difficult to know if, when creating a custom package, we should
use TARGET_MAKE_ENV and/or TARGET_CONFIGURE_OPTS (and maybe other hidden
variables I am not aware of...). It would help to document them. Moreover, it
is in some lines of code example, but not mention in documentation itself...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-06-26 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 12:00 bugzilla at busybox.net [this message]
2023-09-11 18:37 ` [Buildroot] [Bug 11986] Document TARGET_ variables bugzilla
2023-09-12 4:52 ` bugzilla
2024-06-15 14:50 ` 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-11986-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