public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Petri Latvala <petri.latvala@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 1/6] meson: split out simple makefile integration into a makefile
Date: Wed, 17 Jan 2018 11:24:39 +0100	[thread overview]
Message-ID: <20180117102439.GR2759@phenom.ffwll.local> (raw)
In-Reply-To: <20180112105321.mbi5seugthho5sim@platvala-desk.ger.corp.intel.com>

On Fri, Jan 12, 2018 at 12:53:21PM +0200, Petri Latvala wrote:
> On Tue, Oct 24, 2017 at 12:52:51PM +0300, Jani Nikula wrote:
> > A separate makefile is easier to read and maintain than a here
> > document. The meson.sh shell script becomes trivial too.
> > 
> > Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> > ---
> >  Makefile.meson | 33 +++++++++++++++++++++++++++++++++
> >  meson.sh       | 38 +++-----------------------------------
> >  2 files changed, 36 insertions(+), 35 deletions(-)
> >  create mode 100644 Makefile.meson
> 
> 
> I believe the goal for the toplevel makefile wrapper was to support
> editors that issue straight up 'make'.

Yeah I wanted all the built-in editor support for make to Just Work, to
reduce the transition cost for everyone. There's ofc emacs/vim/whatever
plugins for meson. And typing :make -f Makefile.meson defeats the point of
that, might as well install the plugin then.

But if there's no demand for this I'm happy with outright nuking it ...
-Daniel

> 
> 
> 
> 
> -- 
> Petri Latvala
> 
> 
> 
> 
> > 
> > diff --git a/Makefile.meson b/Makefile.meson
> > new file mode 100644
> > index 000000000000..2ed642bdab37
> > --- /dev/null
> > +++ b/Makefile.meson
> > @@ -0,0 +1,33 @@
> > +# -*- makefile -*-
> > +# Simple makefile integration for meson
> > +
> > +.PHONY: default docs
> > +default: all
> > +
> > +Makefile: Makefile.meson
> > +	cp $< $@
> > +
> > +build/build.ninja: Makefile
> > +	mkdir -p build
> > +	meson build
> > +
> > +all: build/build.ninja
> > +	ninja -C build
> > +
> > +clean: build/build.ninja
> > +	ninja -C build clean
> > +
> > +test: build/build.ninja
> > +	ninja -C build test
> > +
> > +reconfigure: build/build.ninja
> > +	ninja -C build reconfigure
> > +
> > +check distcheck dist distclean:
> > +	echo "This is the meson wrapper, not automake" && false
> > +
> > +install uninstall:
> > +	echo "meson install support not yet completed" && false
> > +
> > +docs:
> > +	echo "meson gtkdoc support not yet completed" && false
> > diff --git a/meson.sh b/meson.sh
> > index cbf1a9326dbe..cdb384eb16a6 100755
> > --- a/meson.sh
> > +++ b/meson.sh
> > @@ -1,35 +1,3 @@
> > -#!/bin/bash
> > -
> > -cat > Makefile <<EOF
> > -
> > -.PHONY: default docs
> > -default: all
> > -
> > -build/build.ninja:
> > -	mkdir -p build
> > -	meson build
> > -
> > -all: build/build.ninja
> > -	ninja -C build
> > -
> > -clean: build/build.ninja
> > -	ninja -C build clean
> > -
> > -test: build/build.ninja
> > -	ninja -C build test
> > -
> > -reconfigure: build/build.ninja
> > -	ninja -C build reconfigure
> > -
> > -check distcheck dist distclean:
> > -	echo "This is the meson wrapper, not automake" && false
> > -
> > -install uninstall:
> > -	echo "meson install support not yet completed" && false
> > -
> > -docs:
> > -	echo "meson gtkdoc support not yet completed" && false
> > -
> > -EOF
> > -
> > -make $@
> > +#!/bin/sh
> > +# Simple makefile integration for meson
> > +make -f Makefile.meson "$@"
> > -- 
> > 2.11.0
> > 
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-01-17 10:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-24  9:52 [PATCH i-g-t 0/6] meson: makefile integration cleanup Jani Nikula
2017-10-24  9:52 ` [PATCH i-g-t 1/6] meson: split out simple makefile integration into a makefile Jani Nikula
2018-01-12 10:53   ` Petri Latvala
2018-01-17 10:24     ` Daniel Vetter [this message]
2017-10-24  9:52 ` [PATCH i-g-t 2/6] Makefile.meson: use $(error ...) for errors Jani Nikula
2018-01-12 10:56   ` Petri Latvala
2017-10-24  9:52 ` [PATCH i-g-t 3/6] Makefile.meson: no need to mkdir build directory before running meson Jani Nikula
2017-10-24  9:52 ` [PATCH i-g-t 4/6] Makefile.meson: fix .PHONY deps Jani Nikula
2017-10-24  9:52 ` [PATCH i-g-t 5/6] Makefile.meson: no need to have a separate default target Jani Nikula
2017-10-24  9:52 ` [PATCH i-g-t 6/6] Makefile.meson: add distclean target to remove Makefile and build dir Jani Nikula
2018-01-12 11:03   ` Petri Latvala
2017-10-24 14:18 ` ✗ Fi.CI.BAT: warning for meson: makefile integration cleanup Patchwork

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=20180117102439.GR2759@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=petri.latvala@intel.com \
    /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