From: Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
To: Devicetree Compiler
<devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>,
David Gibson
<david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>,
Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Subject: [PATCH 0/7] pylibfdt: Add installation support
Date: Sun, 26 Mar 2017 13:06:16 -0600 [thread overview]
Message-ID: <20170326190623.27518-1-sjg@chromium.org> (raw)
This series adds support for installation of the Pylib module. It adjusts
the setup.py file to provide this functionality and the Makefile rules
to call it correctly.
It also adds a way to disable building the Python module. This is useful
since some build systems want to use setup.py to do both the build and
the install step. In this case the correct build commands would be:
make NO_PYTHON=1
make install_pylibfdt SETUP_PREFIX=/path/to/install_prefix
Simon Glass (7):
pylibfdt: Allow pkg-config to be supplied in the environment
pylibfdt: Allow building to be disabled
pylibfdt: Use environment to pass C flags and files
pylibfdt: Use package_dir to set the package directory
pylibfdt: Enable installation of Python module
pylibfdt: Use the correct libfdt version in the module
pylibfdt: Use the call function to simplify the Makefile
Makefile | 6 ++++--
README | 13 +++++++++++++
pylibfdt/Makefile.pylibfdt | 19 +++++++++++++++++--
pylibfdt/setup.py | 22 +++++++++++-----------
4 files changed, 45 insertions(+), 15 deletions(-)
--
2.12.1.578.ge9c3154ca4-goog
next reply other threads:[~2017-03-26 19:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-26 19:06 Simon Glass [this message]
[not found] ` <20170326190623.27518-1-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-03-26 19:06 ` [PATCH 1/7] pylibfdt: Allow pkg-config to be supplied in the environment Simon Glass
[not found] ` <20170326190623.27518-2-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-03-27 4:28 ` David Gibson
2017-03-26 19:06 ` [PATCH 2/7] pylibfdt: Allow building to be disabled Simon Glass
[not found] ` <20170326190623.27518-3-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-04-03 18:41 ` Mike Frysinger
2017-04-05 3:28 ` Simon Glass
2017-03-26 19:06 ` [PATCH 3/7] pylibfdt: Use environment to pass C flags and files Simon Glass
[not found] ` <20170326190623.27518-4-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-04-03 18:42 ` Mike Frysinger
2017-04-05 3:28 ` Simon Glass
2017-03-26 19:06 ` [PATCH 4/7] pylibfdt: Use package_dir to set the package directory Simon Glass
2017-03-26 19:06 ` [PATCH 5/7] pylibfdt: Enable installation of Python module Simon Glass
[not found] ` <20170326190623.27518-6-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-04-03 18:43 ` Mike Frysinger
2017-04-05 3:27 ` Simon Glass
2017-03-26 19:06 ` [PATCH 6/7] pylibfdt: Use the correct libfdt version in the module Simon Glass
2017-03-26 19:06 ` [PATCH 7/7] pylibfdt: Use the call function to simplify the Makefile Simon Glass
[not found] ` <20170326190623.27518-8-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-04-03 18:44 ` Mike Frysinger
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=20170326190623.27518-1-sjg@chromium.org \
--to=sjg-f7+t8e8rja9g9huczpvpmw@public.gmane.org \
--cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).