From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/6] snowball-hdmiservice: new package
Date: Fri, 23 Nov 2012 09:38:16 +0100 [thread overview]
Message-ID: <50AF35F8.4060806@mind.be> (raw)
In-Reply-To: <50AF2BB8.8060908@calao-systems.com>
On 23/11/12 08:54, Gr?gory Hermant wrote:
> Le 22/11/2012 18:45, Thomas Petazzoni a ?crit :
>> Dear Gr?gory Hermant,
>>
>> On Thu, 22 Nov 2012 18:33:05 +0100, Gr?gory Hermant wrote:
>>> Le 22/11/2012 15:00, Arnout Vandecappelle a ?crit :
>>>> It should be passed in the environment, not in the make argument list.
>>>> Otherwise it will override the definition in the Makefile itself.
>>>>
>>>> A good Makefile appends to LDFLAGS passed in from the environment, but this
>>>> is not always the case... Anyway the worst that can happen is that the LDFLAGS
>>>> are just ignored.
>>> You mean that way:
>>>
>>> SNOWBALL_HDMISERVICE_MAKE_ENV = CC="$(TARGET_CC)" CCFLAGS="$(TARGET_CCFLAGS)" LDFLAGS="$(TARGET_LDFLAGS)"
>>>
>>> $(SNOWBALL_HDMISERVICE_MAKE_ENV) $(MAKE) -C $(@D)
>> No, just:
>>
>> $(TARGET_CONFIGURE_OPTS) $(MAKE) -C $(@D)
>>
>> Thomas
>
> It doesn't work with this Makefile.
>
> Indeed if i use $(TARGET_CONFIGURE_OPTS) $(MAKE) -C $(@D), CC is set to the host gcc compiler.
Silly Makefile...
You can do either:
$(TARGET_CONFIGURE_OPTS) $(MAKE) -C $(@D) CC="$(TARGET_CC)"
or fix the Makefile in a patch.
But if the Makefile overrides CC, it will most likely also override all the
other stuff so passing TARGET_CONFIGURE_OPTS in the environment doesn't help
much.
What should be our philosophy for bad Makefiles? Fix the Makefile and try
to upstream the patch, or just work around it in a package-specific way?
We can actually work around it generically, using:
$(MAKE) -C $(@D) CC="$(TARGET_CC) $(TARGET_CPPFLAGS) $(TARGET_CFLAGS)"
but I don't like forcing flags into the CC command.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
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:[~2012-11-23 8:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 8:25 [Buildroot] [PATCH v3 0/6] Add support for the snowball board Gregory Hermant
2012-11-15 8:25 ` [Buildroot] [PATCH v3 1/6] snowball-hdmiservice: new package Gregory Hermant
2012-11-21 6:51 ` Arnout Vandecappelle
2012-11-22 12:35 ` Grégory Hermant
2012-11-22 14:00 ` Arnout Vandecappelle
2012-11-22 17:33 ` Grégory Hermant
2012-11-22 17:45 ` Thomas Petazzoni
2012-11-23 7:54 ` Grégory Hermant
2012-11-23 8:38 ` Arnout Vandecappelle [this message]
2012-11-15 8:25 ` [Buildroot] [PATCH v3 2/6] ux500-firmware: " Gregory Hermant
2012-11-21 6:54 ` Arnout Vandecappelle
2012-11-15 8:25 ` [Buildroot] [PATCH v3 3/6] Add board files for snowball Gregory Hermant
2012-11-15 8:25 ` [Buildroot] [PATCH v3 4/6] Add init script files for snowball board Gregory Hermant
2012-11-15 8:25 ` [Buildroot] [PATCH v3 5/6] bluez-utils: add support for the ST-Ericsson cg2900 combo controller Gregory Hermant
2012-11-15 8:25 ` [Buildroot] [PATCH v3 6/6] Add config file for the snowball board Gregory Hermant
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=50AF35F8.4060806@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