All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] new variable <pkg>_CONFIG_FIXUP
Date: Mon, 7 Jan 2013 23:42:06 +0100	[thread overview]
Message-ID: <20130107234206.1487aa87@skate> (raw)
In-Reply-To: <50EB4AE5.7070407@petroprogram.com>

Dear Stefan Fr?berg,

On Tue, 08 Jan 2013 00:23:33 +0200, Stefan Fr?berg wrote:

> You mean checking first in if-statement if  $($(PKG)_CONFIG_FIXUP exist ?
> What is the best way to detect if it exist ?

Just test if the variable is not empty, i.e test -n.

Like (untested):

	if test -n $($(PKG)_CONFIG_FIXUP) ; then \
		$(call MESSAGE, "Blabla") ; \
		for file in ...
			...
		done
	fi

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-01-07 22:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-07 22:01 [Buildroot] new <pkg>_CONFIG_FIXUP variable Stefan Fröberg
2013-01-07 22:01 ` [Buildroot] [PATCH] new variable <pkg>_CONFIG_FIXUP Stefan Fröberg
2013-01-07 22:10   ` Thomas Petazzoni
2013-01-07 22:23     ` Stefan Fröberg
2013-01-07 22:42       ` Thomas Petazzoni [this message]
2013-01-08 20:53         ` Arnout Vandecappelle
2013-01-08 21:10           ` Thomas Petazzoni
2013-01-08 21:10   ` Arnout Vandecappelle
2013-01-07 22:10 ` [Buildroot] new <pkg>_CONFIG_FIXUP variable Yann E. MORIN
2013-01-07 22:27   ` Stefan Fröberg
2013-01-08 23:21     ` Yann E. MORIN
2013-01-09  7:54       ` Thomas Petazzoni
2013-01-09 15:21         ` Stefan Fröberg
2013-01-09 20:31           ` Arnout Vandecappelle
2013-01-10  0:16             ` Stefan Fröberg

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=20130107234206.1487aa87@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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 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.