From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Michael Olbrich <m.olbrich@pengutronix.de>,
Michael Tretter <m.tretter@pengutronix.de>
Subject: [ptxdist] [TOOLCHAIN PATCH] cross-binutils: export license for binutils package
Date: Fri, 17 Apr 2020 09:13:54 +0200 [thread overview]
Message-ID: <20200417071354.2158-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20200417064734.GH2081@pengutronix.de>
The PTXdist binutils package gets its version from the toolchain. So it
always has the same version as the toolchain cross-binutils package.
Export the license data here, so it can be imported in the ptxdist package.
Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
---
Something like this I think. And then:
-include $(PTXDIST_PLATFORMDIR)/selected_toolchain/../share/compliance/binutils.make
in rules/binutils.make in PTXdist.
Michael
rules/cross-binutils.make | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/rules/cross-binutils.make b/rules/cross-binutils.make
index f29c2f821a02..2cdfdfc5d9a7 100644
--- a/rules/cross-binutils.make
+++ b/rules/cross-binutils.make
@@ -75,6 +75,13 @@ endif
@for bin in $(CROSS_BINUTILS_PKGDIR)$(PTXCONF_PREFIX_CROSS)/$(PTXCONF_GNU_TARGET)/bin/*; do \
ln -vsf ../../bin/$(COMPILER_PREFIX)$$(basename $${bin}) $${bin} || break; \
done
+
+ @$(call world/env, CROSS_BINUTILS) \
+ pkg_license_target=binutils \
+ pkg_license_target_license=$(PTXCONF_CROSS_BINUTILS_LICENSE) \
+ pkg_license_target_pattern=$(PTXCONF_CROSS_BINUTILS_LICENSES) \
+ ptxd_make_world_copy_license
+
@$(call touch)
$(STATEDIR)/cross-binutils.install.post:
--
2.20.1
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2020-04-17 7:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 8:43 [ptxdist] [PATCH] binutils: add license information Michael Tretter
2020-04-17 6:47 ` Michael Olbrich
2020-04-17 7:13 ` Michael Olbrich [this message]
2020-04-17 7:39 ` Michael Tretter
2020-04-17 12:16 ` Roland Hieber
2020-04-17 12:23 ` Michael Olbrich
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=20200417071354.2158-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=m.tretter@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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