devicetree-compiler.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: Devicetree Compiler
	<devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH v3 0/5] pylibfdt: Add installation support
Date: Fri, 7 Apr 2017 15:49:43 +1000	[thread overview]
Message-ID: <20170407054943.GC27571@umbus> (raw)
In-Reply-To: <20170405160142.10564-1-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2262 bytes --]

On Wed, Apr 05, 2017 at 10:01:37AM -0600, Simon Glass wrote:
> 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
> 
> Version 3 adds support for running setup.py stand-alone:
> 
>    ./pylibfdt/setup.py --install_path
>    [--prefix=/path/to/install_dir]

I've applied 1&2, 3 breaks make check, somehow, so I've left the rest.

> 
> Changes in v3:
> - Add new patch to fix code style in setup.py
> - Update README to suggest using setup.py for an easy install
> - Allow setup.py to be run from the base directory
> - Make setup.py executable
> - Use define..endef instead of line continuations
> - Add new patch to move to Makefile constructs for NO_PYTHON
> - Add a new patch to use setup.py to build the swig file
> 
> Changes in v2:
> - Add new patch to rename libfdt.swig to libfdt.i
> - Add new patch to allow setup.py to operation stand-alone
> - Rebase to master
> 
> Simon Glass (5):
>   pylibfdt: Rename libfdt.swig to libfdt.i
>   pylibfdt: Fix code style in setup.py
>   pylibfdt: Allow setup.py to operate stand-alone
>   pylibfdt: Use Makefile constructs to implement NO_PYTHON
>   pylibfdt: Use setup.py to build the swig file
> 
>  Makefile                           |  13 ++++-
>  README                             |  14 +++--
>  pylibfdt/Makefile.pylibfdt         |  29 ++++------
>  pylibfdt/{libfdt.swig => libfdt.i} |   0
>  pylibfdt/setup.py                  | 113 ++++++++++++++++++++++++++++++++-----
>  5 files changed, 130 insertions(+), 39 deletions(-)
>  rename pylibfdt/{libfdt.swig => libfdt.i} (100%)
>  mode change 100644 => 100755 pylibfdt/setup.py
> 

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2017-04-07  5:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05 16:01 [PATCH v3 0/5] pylibfdt: Add installation support Simon Glass
     [not found] ` <20170405160142.10564-1-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-04-05 16:01   ` [PATCH v3 1/5] pylibfdt: Rename libfdt.swig to libfdt.i Simon Glass
2017-04-05 16:01   ` [PATCH v3 2/5] pylibfdt: Fix code style in setup.py Simon Glass
2017-04-05 16:01   ` [PATCH v3 3/5] pylibfdt: Allow setup.py to operate stand-alone Simon Glass
     [not found]     ` <20170405160142.10564-4-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-04-07  5:46       ` David Gibson
2017-04-07 21:48         ` Simon Glass
2017-04-05 16:01   ` [PATCH v3 4/5] pylibfdt: Use Makefile constructs to implement NO_PYTHON Simon Glass
2017-04-05 16:01   ` [PATCH v3 5/5] pylibfdt: Use setup.py to build the swig file Simon Glass
2017-04-07  5:49   ` David Gibson [this message]

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=20170407054943.GC27571@umbus \
    --to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
    --cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sjg-F7+t8E8rja9g9hUCZPvPmw@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).