From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 11986] Document TARGET_ variables
Date: Tue, 12 Sep 2023 04:52:07 +0000 [thread overview]
Message-ID: <bug-11986-163-kYfcGPVU0E@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11986-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11986
--- Comment #2 from XonqNopp <xonqnoppp@gmail.com> ---
Hi Jose,
Thanks for checking old tickets :-)
TARGET_MAKE_ENV and TARGET_CONFIGURE_OPTS are still only in examples, but not
explained in the documentation itself...
From today's https://buildroot.org/downloads/manual/manual.html
Section 18.6.1
16: define LIBFOO_BUILD_CMDS
17: $(MAKE) $(TARGET_CONFIGURE_OPTS) -C $(@D) all
18: endef
Section 18.22.1
11: define FOO_BUILD_CMDS
12: $(TARGET_MAKE_ENV) $(MAKE) -C $(LINUX_DIR)/tools foo
13: endef
14:
15: define FOO_INSTALL_STAGING_CMDS
16: $(TARGET_MAKE_ENV) $(MAKE) -C $(LINUX_DIR)/tools \
17: DESTDIR=$(STAGING_DIR) \
18: foo_install
19: endef
20:
21: define FOO_INSTALL_TARGET_CMDS
22: $(TARGET_MAKE_ENV) $(MAKE) -C $(LINUX_DIR)/tools \
23: DESTDIR=$(TARGET_DIR) \
24: foo_install
25: endef
So it is still not clear what is their purpose and how to use them.
I would assume that TARGET_MAKE_ENV contains some environment settings to run
the target's make command, but it is only an assumption. It would help if it
was explained somewhere, and also if the (or at least one) default value is
shown to better understand what those 2 variables do...
Since then I am now more experienced with buildroot and found my way to achieve
what I wanted to do, so I cannot say for sure what we should write, because I
do not remember exactly what and how I did (I should have written that directly
in this ticket, sorry). I just found a comment in a makefile I wrote for a
custom package. Where I define MYPACKAGE_BUILD_CMDS, I just wrote a comment
saying "Do not use TARGET_CONFIGURE_OPTS as it would override options we do not
want" but I don't remember why.
Cheers!
--
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 prev parent reply other threads:[~2023-09-12 4:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 12:00 [Buildroot] [Bug 11986] New: Document TARGET_ variables bugzilla at busybox.net
2023-09-11 18:37 ` [Buildroot] [Bug 11986] " bugzilla
2023-09-12 4:52 ` bugzilla [this message]
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-kYfcGPVU0E@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