From: "Grégory Hermant" <gregory.hermant@calao-systems.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/6] snowball-hdmiservice: new package
Date: Thu, 22 Nov 2012 13:35:57 +0100 [thread overview]
Message-ID: <50AE1C2D.8010905@calao-systems.com> (raw)
In-Reply-To: <50AC79F3.6000807@mind.be>
Arnout,
Le 21/11/2012 07:51, Arnout Vandecappelle a ?crit :
> On 15/11/12 09:25, Gregory Hermant wrote:
>>
>> Signed-off-by: Gregory Hermant<gregory.hermant@calao-systems.com>
> [snip]
>> +
>> +define SNOWBALL_HDMISERVICE_BUILD_CMDS
>> + $(MAKE) CC="$(TARGET_CC)" -C $(@D)
>> +endef
>
> I may have asked this before, but is there a reason to not pass buildroot's
> CFLAGS and LDFLAGS? We usually pass $(TARGET_CONFIGURE_OPTS) to sub-makes.
>
> [snip]
>
The build of the hdmiservice.so fails if i pass the buildroot's LDFLAGS.
> Regards,
> Arnout
>
BR,
gregory
next prev parent reply other threads:[~2012-11-22 12:35 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 [this message]
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
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=50AE1C2D.8010905@calao-systems.com \
--to=gregory.hermant@calao-systems.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.