[Buildroot] Qt Embedded build problem for x86 target (was Re: A new QTOPIA error)

[Buildroot] Qt Embedded build problem for x86 target (was Re: A new QTOPIA error)

[Thiago A. Corrêa]

Hi,

On Tue, Apr 14, 2009 at 4:44 PM, Luciano Greiner
<luciano.greiner@gmail.com> wrote:
> Hi. I installed a new basic debian host system to QTOPIA4. I've got no
> more g++ not found errors, but compilation fails with:
>

I built i686_defconfig with Qtopia enabled and was able to reproduce
his first bug with the g++@ missing.
The workaround was to add -platform linux-g++ to configure. I guess
Nokia/QtSoftware's configure script has a bug somewhere that during
x86 to x86 crosscompiling it's unable to figure out the proper
platform for the host tools.

The problem is, if we just commit this work around, then build would
fail for other hosts, such as freebsd, macos, etc.

Any Ideas?

Kind Regards,
    Thiago A. Correa

[Buildroot] Qt Embedded build problem for x86 target (was Re: A new QTOPIA error)

[Peter Korsgaard]

>>>>> "Thiago" == Thiago A Corr?a <thiago.correa@gmail.com> writes:

Hi,

 Thiago> I built i686_defconfig with Qtopia enabled and was able to reproduce
 Thiago> his first bug with the g++@ missing.
 Thiago> The workaround was to add -platform linux-g++ to configure. I guess
 Thiago> Nokia/QtSoftware's configure script has a bug somewhere that during
 Thiago> x86 to x86 crosscompiling it's unable to figure out the proper
 Thiago> platform for the host tools.

Ahh ok, thanks for looking into it.

 Thiago> The problem is, if we just commit this work around, then build would
 Thiago> fail for other hosts, such as freebsd, macos, etc.

What exactly breaks for those people? My guess is that non-Linux users
compiling for x86 are a pretty small group, but if it's an issue we
can always detect host OS and only add the configure flag for Linux
users.

-- 
Bye, Peter Korsgaard

[Buildroot] Qt Embedded build problem for x86 target (was Re: A new QTOPIA error)

[Thiago A. Corrêa]

Hi,

2009/4/17 Peter Korsgaard <jacmet@uclibc.org>:
>
> ?Thiago> The problem is, if we just commit this work around, then build would
> ?Thiago> fail for other hosts, such as freebsd, macos, etc.
>
> What exactly breaks for those people? My guess is that non-Linux users
> compiling for x86 are a pretty small group, but if it's an issue we
> can always detect host OS and only add the configure flag for Linux
> users.
>

For them, the proper -platform would be different (freebsd-g++, macos-g++, etc).
This basically tells configure what is the proper mkspec/* folder to
use for the host tools, while -xplatform and -embedded tells it what
are the proper mkspec/qws/* folder for the target.

Those folders contain compiler settings, flags and some times, include files.

We could restrict that to only when building x86, but it would still
be hackish, I guess.

Thanks,
    Thiago A. Correa

[Buildroot] Qt Embedded build problem for x86 target (was Re: A new QTOPIA error)

[Peter Korsgaard]

>>>>> "Thiago" == Thiago A Corr?a <thiago.correa@gmail.com> writes:

Hi,

 Thiago> For them, the proper -platform would be different
 Thiago> (freebsd-g++, macos-g++, etc).  This basically tells
 Thiago> configure what is the proper mkspec/* folder to use for the
 Thiago> host tools, while -xplatform and -embedded tells it what are
 Thiago> the proper mkspec/qws/* folder for the target.

 Thiago> Those folders contain compiler settings, flags and some
 Thiago> times, include files.

 Thiago> We could restrict that to only when building x86, but it
 Thiago> would still be hackish, I guess.

Ok, we do have some non-Linux support with the BR2_GNU_BUILD_SUFFIX
stuff (see the toplevel Makefile). We could use the same logic in
qtopia.mk to get the correct -platform.

Don't worry too much about getting support for all obscure OSes
correct right away - Either those people will complain and/or send
patches or no one needs it.

-- 
Bye, Peter Korsgaard