All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Peres <martin.peres@mupuf.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] meson: Allow source location to be configurable
Date: Mon, 1 Mar 2021 08:43:12 +0200	[thread overview]
Message-ID: <7d90b3ab-a525-bf0f-8952-aba2e106c48a@mupuf.org> (raw)
In-Reply-To: <52b977b0d59d74e8283c4f2f2630db91df030a1b.camel@linuxfoundation.org>

Hi Richard,

On 28/02/2021 14:29, Richard Purdie wrote:
> On Sun, 2021-02-28 at 12:06 +0200, Martin Peres wrote:
>> On 27/02/2021 16:49, Richard Purdie wrote:
>>>
>>>    lib_version = vcs_tag(input : 'version.h.in', output : 'version.h',
>>>    		      fallback : 'NO-GIT',
>>> diff --git a/meson_options.txt b/meson_options.txt
>>> index ff3abf08..a0a1aaed 100644
>>> --- a/meson_options.txt
>>> +++ b/meson_options.txt
>>> @@ -50,3 +50,7 @@ option('use_rpath',
>>>           type : 'boolean',
>>>           value : false,
>>>           description : 'Set runpath on installed executables for libigt.so')
>>> +
>>> +option('srcdir',
>>> +       type : 'string',
>>> +       description : 'Path to source code to be compiled into binaries (optional)')
>>
>> Shouldn't this read: "Path to THE source code to be compiled
>> (optional)"? Compiling into binaries is a little redundant, so I would
>> drop it.
> 
> I'm not sure that does quite mean the same thing. The option is talking
> about a path which gets compiled inside the binary rather than a path to code
> which is compiled.
> 
> Regardless, it clearly needs to be more clear! :)
> 
> How about "Source code path in the target environment for use within target
> binaries (optional)"?

Ah ah! Yeah, that was not how I understood it, and your new help text is 
definitely making sense :)

Please send a v2 with this done, after you get an actual review :)

Cheers,
Martin

> 
> Cheers,
> 
> Richard
> 
>> Other than this, the rationale seems sane, but I am not
>> knowledgeable-enough about IGT's build system to comment more on it:
>>
>> Acked-by: Martin Peres <martin.peres@mupuf.org>
>>
>>>
>>
> 
> 
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2021-03-01  6:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-27 14:49 [igt-dev] [PATCH i-g-t] meson: Allow source location to be configurable Richard Purdie
2021-02-27 15:45 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2021-02-27 17:26 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-02-28 10:06 ` [igt-dev] [PATCH i-g-t] " Martin Peres
2021-02-28 12:29   ` Richard Purdie
2021-03-01  6:43     ` Martin Peres [this message]
2021-03-01  7:30       ` Petri Latvala

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=7d90b3ab-a525-bf0f-8952-aba2e106c48a@mupuf.org \
    --to=martin.peres@mupuf.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=richard.purdie@linuxfoundation.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.