Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] Compiling process
Date: Wed, 22 Aug 2012 13:36:35 +0200	[thread overview]
Message-ID: <5034C443.8020100@relinux.de> (raw)
In-Reply-To: <1345632626.17520.YahooMailNeo@web164605.mail.gq1.yahoo.com>

Am 22.08.2012 12:50, schrieb Zoran Djordjevic:
> Can you tell me, Stephan, what is your developement environment?
> Can I use some ordinary editor to create .c or .cpp file and then
> compile from command line?
> Do I have to write some code in Qt related source to react on -qws
> option ?
For now I only use the example and demo programs included in the QT
distribution (have to be enabled in buildroot xconfig).

For a user application I would create a package according to the
buildroot documentation. Of Course you have to write a QT application;-)

QT has the advantage to be cross-platform, so you should be able to
create and test the application on your desktop (e.g. with qt designer)
and compile it afterwards within buildroot.

Regards

Stephan
 
> Thanks
>
> *From:* Stephan Hoffmann <sho@relinux.de>
> *To:* buildroot at busybox.net
> *Sent:* Wednesday, August 22, 2012 12:26 PM
> *Subject:* Re: [Buildroot] Compiling process
>
> Am 22.08.2012 12:18, schrieb Zoran Djordjevic:
>> Hello
>>  
>> Can someone tell me through an example what compiler line
>> should look like for compiling SomeFile.c (or .cpp) using compiler,
>> built by Buildroot.
>> Also, does Qt need building X server, or it run independently of it ?
> Hi,
>
> I am currently working with QT without X. It runs directly on the
> Linux framebuffer.
>> Does some window manager have to be installed ?
> No, but you have to start the app with the "-qws" option.
>
> Kind regards
>
> Stephan
>>  
>> Best regards
>>
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net <mailto:buildroot@busybox.net>
>> http://lists.busybox.net/mailman/listinfo/buildroot
>
>
> -- 
> reLinux     -    Stephan Hoffmann
> Am Schmidtgrund 124    50765 K?ln
> Tel. +49.221.95595-19    Fax: -64
> http://www.relinux.de/     sho at reLinux.de <mailto:sho@reLinux.de>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net <mailto:buildroot@busybox.net>
> http://lists.busybox.net/mailman/listinfo/buildroot
>


-- 
reLinux     -    Stephan Hoffmann
Am Schmidtgrund 124    50765 K?ln
Tel. +49.221.95595-19    Fax: -64
www.reLinux.de     sho at reLinux.de


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120822/ba28cc31/attachment.html>

  reply	other threads:[~2012-08-22 11:36 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 [this message]
2012-08-22 13:18   ` Grant Edwards
2012-08-22 10:30 ` Fabio Porcedda
2012-08-22 17:47 ` Thomas Petazzoni
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=5034C443.8020100@relinux.de \
    --to=sho@relinux.de \
    --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