From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] httping: new package
Date: Sat, 19 Jan 2013 14:51:19 +0100 [thread overview]
Message-ID: <50FAA4D7.10006@mind.be> (raw)
In-Reply-To: <87ehhnudd9.fsf@dell.be.48ers.dk>
On 14/01/13 14:02, Peter Korsgaard wrote:
>>>>>> "Gilles" == Gilles Talis<gilles.talis@gmail.com> writes:
>
> Gilles> I forgot to copy mailing list.
> Gilles> Sorry about that and thanks for your help.
> Gilles> Gilles.
>
> Gilles> 2013/1/13 Gilles Talis<gilles.talis@gmail.com>
>
> Gilles> Dear Thomas,
>
> Gilles> I thought I knew Makefiles better than that. Well, I was wrong :-).
> Gilles> The reason why TARGET_CONFIGURE_OPTS does not work in this case is because
> Gilles> it overrides the original Makefile's CFLAGS variable (that should be kept
> Gilles> in order for target to compile). Apart from adding "override" in the
> Gilles> package Makefile, I actually do not see how to use TARGET_CONFIGURE_OPTS
> Gilles> and still keep Makefile CFLAGS. Any hint?
> Gilles> This will surely help me for future patches/projects.
>
> That's indeed how it is normally done.
>
> override CFLAGS += ..
No.
Normally CFLAGS should be assigned to either as
CFLAGS +=
or
CFLAGS ?=
and the user-settable CFLAGS are passed in the environment.
I think most Makefiles follow that convention.
Patch follows.
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
next prev parent reply other threads:[~2013-01-19 13:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 0:29 [Buildroot] [PATCH 1/1] httping: new package Gilles Talis
2013-01-13 11:05 ` Thomas Petazzoni
2013-01-13 20:21 ` Gilles Talis
2013-01-13 20:32 ` Thomas Petazzoni
[not found] ` <CAKcgs2xk-=iG-3Ezmc1upEPBjhSGcmgg9WSwn=1E3+OKDT05fg@mail.gmail.com>
2013-01-14 0:47 ` Gilles Talis
2013-01-14 13:02 ` Peter Korsgaard
2013-01-19 13:51 ` Arnout Vandecappelle [this message]
2013-01-19 13:52 ` [Buildroot] [PATCH] httping: remove redundant 'override CFLAGS' patch Arnout Vandecappelle
2013-01-20 20:03 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2013-01-14 23:32 [Buildroot] [PATCH 1/1] httping: new package gilles.talis at gmail.com
2013-01-15 8:23 ` Peter Korsgaard
2013-01-12 0:00 gilles.talis at gmail.com
2013-01-12 11:07 ` Thomas Petazzoni
2013-01-12 16:37 ` Gilles Talis
2013-01-13 0:37 ` Gilles Talis
2013-01-19 13:39 ` Arnout Vandecappelle
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=50FAA4D7.10006@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 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.