Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Qt Embedded build problem for x86 target (was Re: A new QTOPIA error)
Date: Mon, 20 Apr 2009 22:50:53 +0200	[thread overview]
Message-ID: <87fxg3rqvm.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <d6cda7730904201330t1cc17320n370070798d3f4bdb@mail.gmail.com> ("Thiago A. Corrêa"'s message of "Mon\, 20 Apr 2009 17\:30\:07 -0300")

>>>>> "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

      reply	other threads:[~2009-04-20 20:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17  9:43 [Buildroot] Qt Embedded build problem for x86 target (was Re: A new QTOPIA error) Thiago A. Corrêa
2009-04-17 14:00 ` Peter Korsgaard
2009-04-20 20:30   ` Thiago A. Corrêa
2009-04-20 20:50     ` Peter Korsgaard [this message]

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=87fxg3rqvm.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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