Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] kconfig-package: add support for config fragments
Date: Mon, 23 Mar 2015 22:41:39 +0100	[thread overview]
Message-ID: <55108893.2060003@mind.be> (raw)
In-Reply-To: <20150323183116.GA4214@free.fr>

On 23/03/15 19:31, Yann E. MORIN wrote:
> J?r?my, All,
> 
> On 2015-03-23 09:09 +0100, Jeremy Rosen spake thusly:
>> ----- Mail original -----
>>> On 21/03/15 00:11, Yann E. MORIN wrote:
>>>> Floris, All,
>>>>
>> [...]
>>>> use a shell construct here, like:
>>>>
>>>>     $$(if $$($(2)_KCONFIG_FRAGMENT_FILES), \
>>>>         echo "Unable to perform $(1)-update-config when fragment
>>>>         files are set"; exit 1)
>>>
>>>  Or perhaps it's better to simply disable the update targets when
>>>  fragments are set:
>>>
>>> # Cannot update (def)config with fragments
>>> ifneq ($$($(2)_KCONFIG_FRAGMENT_FILES),)
>>> $(1)-update-config: ...
>>> ...
>>> endif
>>>
>>> [snip]
>>
>> I'm not sure... we are in a case where the user knows that the target
>> is supposed to exist. an unknown target message would be more
>> confusing than the OP's proposed error message. I would not be 
>> suprised if someone reported the missing target as a bug here...
> 
> Agred, But I guess that what Arnout suggested would be something like:
> 
>     $(1)-update-config:
>     ifneq ($$($(2)_KCONFIG_FRAGMENT_FILES),)
>         ...
>     else
>         echo ERROR.
>     enfi

 Actually I did mean what I said, but I also agree with Jeremy that it could be
confusing. So +1 to Yann's suggestion.


 Regards,
 Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2015-03-23 21:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-15 12:33 [Buildroot] [PATCH 1/5] kconfig-package: add support for config fragments Floris Bos
2015-02-15 12:33 ` [Buildroot] [PATCH 2/5] linux: add option to specify " Floris Bos
2015-03-20 23:15   ` Yann E. MORIN
2015-02-15 12:33 ` [Buildroot] [PATCH 3/5] busybox: " Floris Bos
2015-03-20 23:20   ` Yann E. MORIN
2015-02-15 12:33 ` [Buildroot] [PATCH 4/5] uclibc: " Floris Bos
2015-03-20 23:22   ` Yann E. MORIN
2015-02-15 12:33 ` [Buildroot] [PATCH 5/5] barebox: " Floris Bos
2015-03-20 23:23   ` Yann E. MORIN
2015-03-20 23:11 ` [Buildroot] [PATCH 1/5] kconfig-package: add support for " Yann E. MORIN
2015-03-21 14:57   ` Arnout Vandecappelle
2015-03-23  8:09     ` Jeremy Rosen
2015-03-23 18:31       ` Yann E. MORIN
2015-03-23 21:41         ` Arnout Vandecappelle [this message]
2015-03-20 23:14 ` Yann E. MORIN

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=55108893.2060003@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /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