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] Qt5 puzzle
Date: Wed, 6 Nov 2013 20:52:33 +0100	[thread overview]
Message-ID: <20131106205233.28e38d06@skate> (raw)
In-Reply-To: <CALo-6+g+cuLUjWi5+PC+Y1+MUcuENnv3etVT3FXrk3Yqf_vF5Q@mail.gmail.com>

Dear Charles Krinke,

On Wed, 6 Nov 2013 11:08:22 -0800, Charles Krinke wrote:

> I think I see what is going on. It looks like Qt sets USE_EABI_HARDFLOAT=0
> when I need it to be USE_EABI_HARDFLOAG=1.
> 
> This is done in qt5jsbackend-5.0.2/src/vi/v8.pri as a consequence of
> 
> config_hardfloat {
>   DEFINES += USE_EABI_HARDFLOAT=1
> } else {
>   DEFINES += USE_EABI_HARDFLOAT=0
> }
> 
> Where config_hardfloat is always undefined.

See my reply to your e-mail.

> This may bring up a larger question in that some embedded systems will wish
> to use softfloat and some hardfloat

I don't understand what you mean here. We have options in Buildroot to
allow the user to configure whether (s)he wants a soft float or hard
float system.

As I said in my other e-mail, what you should investigate is precisely
why the config_hardfloat test is returning the wrong result.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2013-11-06 19:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06 16:57 [Buildroot] Qt5 puzzle Charles Krinke
2013-11-06 17:28 ` Thomas De Schampheleire
2013-11-06 19:08   ` Charles Krinke
2013-11-06 19:52     ` Thomas Petazzoni [this message]
2013-11-06 18:18 ` Thomas Petazzoni
2013-11-06 20:55   ` Charles Krinke
2013-11-06 22:06     ` Thomas Petazzoni
2013-11-06 22:27       ` Charles Krinke
2013-11-06 22:53         ` Thomas Petazzoni

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=20131106205233.28e38d06@skate \
    --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