Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] uboot-tools: bump to version 2014.04
Date: Wed, 30 Apr 2014 07:19:59 +0000	[thread overview]
Message-ID: <1398842399.21385.2.camel@abrodkin-8560l> (raw)
In-Reply-To: <877g67thh9.fsf@dell.be.48ers.dk>

Hi Peter,

On Wed, 2014-04-30 at 09:16 +0200, Peter Korsgaard wrote:
> >>>>> "Alexey" == Alexey Brodkin <Alexey.Brodkin@synopsys.com> writes:
> 
>  > U-Boot v2014.04 introduced significant changes in its build infrastrcture.
>  > Among things related to buildroot are:
>  > 1. Special new target ("tools-only") was added for building host tools alone
> 
>  > 2. Tools cross-building for target is no longer possible with substitution of
>  > HOSTxx with TARGETxx because host binaries won't be built. Instead we just set
>  > CROSS_COMPILE and CROSS_BUILD_TOOLS variables.
> 
>  > 3. Most of make targets now require U-Boot to be configured before building.
>  > So for building generic "fw_printenv" we now need to make "env" target config-
>  > independent.
> 
>  > 4. HOSTCPPFLAGS are only applicable to .cpp files so dropping
>  > "uboot-tools-02-hostcflags-override-fix.patch"
> 
> That's not true. They are flags for the preprocessor. You must be
> confusing them with CXXFLAGS.
> 
> With that said, I think we're passing everything from HOST_CPPFLAGS
> through HOST_CFLAGS as well, so it shouldn't matter.

Ok I think I did confused wit CXXFLAGS.

But I haven't found any mention of HOSTCPPFLAGS in current U-Boot so I'm
wondering if we still need to add any handling of HOSTCPPFLAGS in U-Boot
or there's nothing to be done?

Regards,
Alexey

  reply	other threads:[~2014-04-30  7:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30  6:54 [Buildroot] [PATCH v3] uboot-tools: bump to version 2014.04 Alexey Brodkin
2014-04-30  7:16 ` Peter Korsgaard
2014-04-30  7:19   ` Alexey Brodkin [this message]
2014-04-30  7:29     ` Peter Korsgaard
2014-04-30  7:33       ` Alexey Brodkin
2014-05-09 11:25       ` Alexey Brodkin
2014-05-11 22:02 ` Peter Korsgaard

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=1398842399.21385.2.camel@abrodkin-8560l \
    --to=alexey.brodkin@synopsys.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