All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH i-g-t 12/22] meson: basic build system support
Date: Fri, 08 Sep 2017 11:53:52 +0300	[thread overview]
Message-ID: <87mv654llr.fsf@nikula.org> (raw)
In-Reply-To: <20170908065049.yt4slunrabi2okw3@phenom.ffwll.local>

On Fri, 08 Sep 2017, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Wed, Sep 06, 2017 at 05:01:42PM +0300, Jani Nikula wrote:
>> On Tue, 05 Sep 2017, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
>> > +configure_file(output: 'config.h', install: false, configuration: config_h)
>> 
>> This makes me think config_h is a misnomer for the configuration data
>> object. I'd probably use plain "config" instead.
>> 
>> I think we'll end up wanting to use the configuration data for the test
>> runner shell scripts too, and generate a sh.config from the same
>> config. We can source the sh.config from e.g. run-tests.sh, to figure
>> out the source and build directories. We can use find_program() to find
>> piglit, for example, and shove that into sh.config.
>> 
>> Look at the beginning of run-tests.sh and see how much better it could
>> be with a sh.config.
>> 
>> Of course, the alternative is to use a separate configuration data
>> object for sh.config, but I think it's clearer to use one, and use .in
>> files to decide what goes in them.
>
> configuration_data() seems to just be a special-purpose
> wrangler/generator. I use it also for mangling manpages later on iirc.

We had a misunderstanding here, clarified on IRC.

I meant, do use configuration data, but only use one configuration data
object, and generate several outputs from one object. I think we'll
benefit from being able to pull in some config data to a sh.config later
on, and using that in run-tests.sh and elsewhere. Which means "config_h"
will be a slightly misleading name, just call it "config".

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-09-08  8:54 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05 12:36 [PATCH i-g-t 00/22] RFC: meson build system support Daniel Vetter
2017-09-05 12:36 ` [PATCH i-g-t 01/22] build: Define _GNU_SOURCE in Makefile.am Daniel Vetter
2017-09-05 16:19   ` [PATCH i-g-t] " Daniel Vetter
2017-09-05 21:08     ` Chris Wilson
2017-09-06  9:02       ` Daniel Vetter
2017-09-05 12:36 ` [PATCH i-g-t 02/22] build: Nuke #ifdef HAVE_CONFIG_H cargo-cult Daniel Vetter
2017-09-05 12:36 ` [PATCH i-g-t 03/22] build: use HAVE_LIBGEN_H consistently Daniel Vetter
2017-09-05 12:36 ` [PATCH i-g-t 04/22] build: remove _GNU_SOURCE from source files Daniel Vetter
2017-09-05 12:36 ` [PATCH i-g-t 05/22] tests/gem_spin_batch: Fix warning Daniel Vetter
2017-09-05 12:36 ` [PATCH i-g-t 06/22] lib: prefix frame_dump_path Daniel Vetter
2017-09-05 12:36 ` [PATCH i-g-t 07/22] lib: clean up header includes Daniel Vetter
2017-09-06 11:44   ` Chris Wilson
2017-09-08  6:55     ` Daniel Vetter
2017-09-08  9:23   ` [PATCH i-g-t] " Daniel Vetter
2017-09-05 12:36 ` [PATCH i-g-t 08/22] tests/igt_command_line.sh: Allow testing individual tests Daniel Vetter
2017-09-05 16:43   ` [PATCH i-g-t] " Daniel Vetter
2017-09-06  8:02     ` Daniel Vetter
2017-09-05 12:36 ` [PATCH i-g-t 09/22] lib/uwildmat: Use include paths Daniel Vetter
2017-09-05 12:36 ` [PATCH i-g-t 10/22] demos: remove Daniel Vetter
2017-09-05 16:20   ` [PATCH i-g-t] " Daniel Vetter
2017-09-05 16:45     ` Daniel Vetter
2017-09-05 12:36 ` [PATCH i-g-t 11/22] assembler/test: Prep work for meson Daniel Vetter
2017-09-05 12:36 ` [PATCH i-g-t 12/22] meson: basic build system support Daniel Vetter
2017-09-06 14:01   ` Jani Nikula
2017-09-08  6:50     ` Daniel Vetter
2017-09-08  8:53       ` Jani Nikula [this message]
2017-09-05 12:36 ` [PATCH i-g-t 13/22] lib/ioctl_wrappers: make the valgrind wrapper always emit a statement:w Daniel Vetter
2017-09-05 12:36 ` [PATCH i-g-t 14/22] tests/kms_plane: Appease gcc -Wempty-body Daniel Vetter
2017-09-05 12:36 ` [PATCH i-g-t 15/22] meson: Add some compiler flags to reduce warnings Daniel Vetter
2017-09-05 12:36 ` [PATCH i-g-t 16/22] meson: Don't build the igt audio test without gsl available Daniel Vetter
2017-09-05 12:36 ` [PATCH i-g-t 17/22] meson: Use static libs to handle IGT_LOG_DOMAIN Daniel Vetter
2017-09-05 12:36 ` [PATCH i-g-t 18/22] meson: detect cc flags Daniel Vetter
2017-09-05 12:36 ` [PATCH i-g-t 19/22] meson: add manpage support Daniel Vetter
2017-09-05 12:36 ` [PATCH i-g-t 20/22] meson: igt_frame also needs pixman Daniel Vetter
2017-09-05 12:36 ` [PATCH i-g-t 21/22] meson: Minimal README update Daniel Vetter
2017-09-05 12:36 ` [PATCH i-g-t 22/22] meson: Bump required version to 0.40 Daniel Vetter
2017-09-05 16:21 ` ✗ Fi.CI.BAT: failure for RFC: meson build system support (rev3) Patchwork
2017-09-06  7:52 ` ✗ Fi.CI.BAT: failure for RFC: meson build system support (rev5) Patchwork
2017-09-06  7:53 ` Patchwork
2017-09-06  8:19 ` ✓ Fi.CI.BAT: success for RFC: meson build system support (rev6) Patchwork
2017-09-06  9:44 ` ✓ Fi.CI.IGT: " Patchwork
2017-09-08  9:07 ` [PATCH i-g-t 00/22] RFC: meson build system support Jani Nikula
2017-09-08  9:30 ` Arkadiusz Hiler
2017-09-08  9:36 ` Petri Latvala
2017-09-08 10:49 ` ✓ Fi.CI.BAT: success for RFC: meson build system support (rev7) Patchwork
2017-09-08 10:58 ` [PATCH i-g-t 00/22] RFC: meson build system support Daniel Stone
2017-09-08 11:01 ` Szwichtenberg, Radoslaw
2017-09-08 13:14 ` ✓ Fi.CI.IGT: success for RFC: meson build system support (rev7) 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=87mv654llr.fsf@nikula.org \
    --to=jani.nikula@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.