From: Roland Hieber <r.hieber@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <r.hieber@pengutronix.de>
Subject: [ptxdist] [PATCH] doc: ref parameter: document special make target 'license-report'
Date: Mon, 26 Mar 2018 09:54:31 +0200 [thread overview]
Message-ID: <20180326075431.4871-1-r.hieber@pengutronix.de> (raw)
In-Reply-To: <4bd8ee22-8d1d-0986-9cc2-d6bc3b2f19af@pengutronix.de>
Signed-off-by: Roland Hieber <r.hieber@pengutronix.de>
---
doc/ref_parameter.inc | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/doc/ref_parameter.inc b/doc/ref_parameter.inc
index 7763f74ba..73269ab19 100644
--- a/doc/ref_parameter.inc
+++ b/doc/ref_parameter.inc
@@ -217,6 +217,11 @@ Misc Actions
``make <target>``
build specified make target in PTXdist.
+``make license-report``
+ build a license report. This report shows up in
+ ``platform-<name>/report/license-report.pdf`` and contains all open-source
+ licenses for each package that is used in the project.
+
``export_src <target-dir>``
export all source archives needed for this project to ``<target-dir>``.
--
2.11.0
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-03-26 7:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 9:51 [ptxdist] How to generate license report? Alexander Dahl
2018-03-22 10:09 ` [ptxdist] [PATCH] ptxdist: Add switch to generate PDF license report Denis OSTERLAND
2018-03-26 7:44 ` [ptxdist] How to generate license report? Roland Hieber
2018-03-26 7:54 ` Roland Hieber [this message]
2018-03-27 7:43 ` Michael Olbrich
2018-03-27 8:42 ` Alexander Dahl
2018-03-27 9:26 ` Alm, Michael
2018-03-28 20:31 ` Andreas Pretzsch
2018-03-29 7:31 ` Denis OSTERLAND
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=20180326075431.4871-1-r.hieber@pengutronix.de \
--to=r.hieber@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