From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Evaluation of make variables
Date: Fri, 30 Jul 2010 10:33:54 +0200 [thread overview]
Message-ID: <20100730103354.1c7f1a0f@surf> (raw)
In-Reply-To: <1280231693.22687.47.camel@dubciaranr1.verifone.com>
On Tue, 27 Jul 2010 12:54:53 +0100
Quotient Remainder <quotientvremainder@gmail.com> wrote:
> Well my reason for looking at this was so that I could use Maxime's
> git/svn patches to use a git repo to hold the U-Boot source. As it
> stands only Makefiles using gentargets can use this. I would want to
> do this for the linux kernel too.
As we discussed in another thread (if I remember correctly), I'm not
sure the gentargets infrastructure is appropriate for building the
kernel and bootloaders. But definitely, some sort of infrastructure
for building these would be good.
> Is this an inherent limitation of the make syntax or specific to the
> layout of the buildroot makefiles?
Inherent limitation of the make syntax. Try a simple test.mk file that
does:
FOOBAR=y
define BARFOO
ifeq ($(FOOBAR),y)
echo "Hello World"
endif
endef
all:
$(BARFOO)
it doesn't work, while:
FOOBAR=y
ifeq ($(FOOBAR),y)
define BARFOO
echo "Hello World"
endef
endif
all:
$(BARFOO)
does work.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-07-30 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 10:36 [Buildroot] Evaluation of make variables Quotient Remainder
2010-07-27 11:42 ` Thomas Petazzoni
2010-07-27 11:54 ` Quotient Remainder
2010-07-30 8:33 ` Thomas Petazzoni [this message]
2010-07-30 15:41 ` Quotient Remainder
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=20100730103354.1c7f1a0f@surf \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox