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] Compiling process
Date: Wed, 22 Aug 2012 19:47:10 +0200	[thread overview]
Message-ID: <20120822194710.14807341@skate> (raw)
In-Reply-To: <1345630715.32281.YahooMailNeo@web164601.mail.gq1.yahoo.com>

Le Wed, 22 Aug 2012 03:18:35 -0700 (PDT),
Zoran Djordjevic <djdjdjole@yahoo.com> a ?crit :

> Can someone tell me through an example?what compiler line 
> should look like for compiling SomeFile.c (or .cpp) using compiler, 
> built by Buildroot. 

Use the compiler in output/host/usr/bin/<arch>-gcc.

> Also, does Qt need building X server, or it run independently of it ?

No, it can run directly on the framebuffer.

> Does some window manager have to be installed??

For a simple full screen application, just run your Qt application with
-qws as others mentioned.

If you want to build your Qt application with qmake, then use the qmake
installed in output/host/usr/bin/qmake.

I should probably put together a step-by-step tutorial on how to use
Buildroot to write Qt apps, as this sounds like a popular request.

Best regards,

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

  parent reply	other threads:[~2012-08-22 17:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22 10:18 [Buildroot] Compiling process Zoran Djordjevic
2012-08-22 10:26 ` Stephan Hoffmann
2012-08-22 10:50   ` Zoran Djordjevic
2012-08-22 11:36     ` Stephan Hoffmann
2012-08-22 13:18   ` Grant Edwards
2012-08-22 10:30 ` Fabio Porcedda
2012-08-22 17:47 ` Thomas Petazzoni [this message]
2012-08-23  6:01   ` [Buildroot] QT " Stephan Hoffmann

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=20120822194710.14807341@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