public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>,
	Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: [PATCH] linux-custom: Clean up minor inconsistencies in rules.tmpl
Date: Mon, 31 Aug 2020 18:29:35 +0200	[thread overview]
Message-ID: <16a1b544-7fec-9895-fff2-03e746910e66@siemens.com> (raw)
In-Reply-To: <f84a8a85-6356-40ff-aa84-efc2ff635c71@siemens.com>

On 22.06.20 09:36, [ext] Jan Kiszka wrote:
> On 29.05.20 07:53, [ext] Jan Kiszka wrote:
>> On 28.05.20 22:04, Baurzhan Ismagulov wrote:
>>> On Sun, May 24, 2020 at 11:43:13AM +0200, Jan Kiszka wrote:
>>>> .PHONY is not needed (and wasn't consistently used anyway). And that
>>>> missing && before the last export was apparently not critical as well.
>>>
>>> Wow, export A=a export B=b is accepted at least by bash. The && fix is still
>>> needed if there is an error in A=a, thanks for the catch.
>>>
>>> Regarding .PHONY, could you please comment why it is not needed? Usually it's a
>>> safeguard against the case when a file with the name of a target exists (e.g.,
>>> override_dh_auto_clean). In that case, the target is not built, and .PHONY
>>> enforces building. If there are no other reasons, I'd rather go towards making
>>> it consistent (PHONY -> .PHONY, .PHONY: override_dh_auto_install).
>>
>> I suspect the Debian's build framework sets them already because I
>> haven't seen them in use in all examples and manuals I read.
>>
> 
> Ping.
> 
> Jan
> 

Ping²

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

      reply	other threads:[~2020-08-31 16:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-24  9:43 Jan Kiszka
2020-05-28 20:04 ` Baurzhan Ismagulov
2020-05-29  5:53   ` Jan Kiszka
2020-06-22  7:36     ` Jan Kiszka
2020-08-31 16:29       ` Jan Kiszka [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=16a1b544-7fec-9895-fff2-03e746910e66@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=ibr@ilbers.de \
    --cc=isar-users@googlegroups.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