Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [pull request v2] Pull request for branch for-2011.02/fix-ccache-support
Date: Tue, 7 Dec 2010 20:53:15 +0100	[thread overview]
Message-ID: <20101207205315.5cc88d60@surf> (raw)
In-Reply-To: <AANLkTi=6nM36bHfthxOTgw3noRR+P-pz6k10YcBGOws7@mail.gmail.com>

Hello,

On Tue, 7 Dec 2010 01:04:41 +0100
Bj?rn Forsman <bjorn.forsman@gmail.com> wrote:

> Are many packages affected?

I don't remember.

> If many, I'll just take your word for it and leave TARGET_CC and
> xFLAGS variables be, but if there is only a few packages affected,
> maybe we can fix them instead?

The problem was related to libtool. And unfortunately "fix problem" and
"libtool" in the same sentence is fairly hard to have :-)

Honestly, I've spent quite a bit of time at this moment trying to find
the solution for the --sysroot option that would work with most
packages, without requiring to do horrible things. As things are
working today, I'm not really willing to spend more time on this, but
if others want, I of course won't prevent them from doing so. I'll just
ask for some heavy testing to be done before accepting changes on
this :-)

> Yes, I'd like to get this CMake toolchain file feature into Buildroot
> as well. How about appending a toolchain file target to
> $(2)_DEPENDENCIES in Makefile.cmake.in?

Hum, why ? Do you want to use the toolchain file even to build the
CMake-based packages in Buildroot ? Or just provide it for users to
build external softwares outside of Buildroot ?

> And place the toolchain file in output/?

As it should be part of the SDK, it should probably be located in
$(HOST_DIR) somewhere. But I'm not really clear yet on what the
organization of the SDK should be. In the mean time, just assume you
can put it in $(O), moving it to some other place won't be hard.

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-12-07 19:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03 19:16 [Buildroot] [pull request v2] Pull request for branch for-2011.02/fix-ccache-support Thomas Petazzoni
2010-12-03 19:16 ` [Buildroot] [PATCH 1/1] ccache: rework ccache management Thomas Petazzoni
2010-12-05 22:47   ` Peter Korsgaard
2010-12-05 22:40 ` [Buildroot] [pull request v2] Pull request for branch for-2011.02/fix-ccache-support Peter Korsgaard
2010-12-06  9:44   ` Bjørn Forsman
2010-12-06 15:08     ` Peter Korsgaard
2010-12-06 19:24       ` Thomas Petazzoni
2010-12-06 19:22     ` Thomas Petazzoni
2010-12-07  0:04       ` Bjørn Forsman
2010-12-07 19:53         ` Thomas Petazzoni [this message]
2010-12-08 10:24           ` Bjørn Forsman
2010-12-06 23:14   ` Thomas Petazzoni
2010-12-07 12:26     ` 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=20101207205315.5cc88d60@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