New: Document TARGET_ variables
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...
Signature · 2 lines
You are receiving this mail because: You are on the CC list for the bug.
[Buildroot] [Bug 11986] Document TARGET_ variables
https://bugs.busybox.net/show_bug.cgi?id=11986
Jose Angel Torres <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #1 from Jose Angel Torres <[email protected]> --- (In reply to XonqNopp from comment #0)
Hi XonqNopp,
Did you get some clarity on this since you have posted this bug? Has the documentation improved to meet your present day understanding? What can we do to satisfy your original request at this point so that we may close this issue?
I'm willing to help improve this bit.
Sincerely,
Jose
Signature · 6 lines
You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
[Buildroot] [Bug 11986] Document TARGET_ variables
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=11986
--- Comment #2 from XonqNopp <[email protected]> --- 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!
Signature · 6 lines
You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
[Buildroot] [Bug 11986] Document TARGET_ variables
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=11986
Yann E. MORIN <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |MOVED
Status|NEW |RESOLVED
CC| |[email protected]--- Comment #3 from Yann E. MORIN <[email protected]> --- Thank you for your report.
The issue tracker for the Buildroot project has been moved to the Gitlab.com issue tracker:
https://gitlab.com/buildroot.org/buildroot/-/issues
We are taking this opportunity to close old issues in this old tracker. If you believe your issue is still relevant, please open one in the new issue tracker.
Thank you!
Signature · 6 lines
You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot