Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Currently packaging Qt5
Date: Thu, 17 Jan 2013 10:03:03 +0100	[thread overview]
Message-ID: <50F7BE47.6080702@mind.be> (raw)
In-Reply-To: <20130114141045.039ec839@skate>

On 14/01/13 14:10, Thomas Petazzoni wrote:
> Dear Sagaert Johan,
>
> On Mon, 14 Jan 2013 13:48:12 +0100, Sagaert Johan wrote:
>
>> Just a hint :
>>
>> https://github.com/nezticle/RaspberryPi-BuildRoot has the QT5 integrated
>> with the squask toolchain in buildroot.
>> Maintained by Andy Nichols [nezticle at gmail.com]
>
> Yes, that's what I'm using as an inspiration, even though I'm making
> things a bit more configurable (provide more options for graphical
> backends, etc.).
>
> I'm still wondering why so many people are doing Buildroot forks
> without contributing back the valuable work they are doing.

  Maybe we should schedule some effort to discuss that on these projects' 
mailing lists.

  It seems BTW that those projects are typically also forking, without 
merging updates in buildroot itself. Shame.

  Regards,
  Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2013-01-17  9:03 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14  9:58 [Buildroot] Currently packaging Qt5 Thomas Petazzoni
2013-01-14 10:50 ` Daniel Nyström
2013-01-14 11:04   ` Thomas Petazzoni
2013-02-19  4:18     ` prabindh
2013-02-19 15:29       ` Thomas Petazzoni
2013-05-20  3:31         ` prabindh
2013-05-22 11:55           ` Sundareson, Prabindh
2013-05-22 12:17             ` Thomas Petazzoni
2013-05-22 12:23               ` prabindh
2013-05-22 12:31                 ` Thomas Petazzoni
2013-05-22 12:36                   ` prabindh
2013-05-22 13:06                     ` Thomas Petazzoni
2013-05-22 13:26                       ` Sundareson, Prabindh
2013-05-22 13:30                         ` Thomas Petazzoni
2013-05-22 13:35                           ` prabindh
2013-05-22 14:04                             ` Thomas Petazzoni
2013-05-22 14:18                               ` Spenser Gilliland
2013-05-22 14:39                                 ` Thomas Petazzoni
2013-05-22 15:57                                 ` prabindh
2013-05-22 17:33                                   ` Spenser Gilliland
2013-05-23 20:38                                     ` Wojciech Sleńska
2013-05-22 12:16           ` Thomas Petazzoni
2013-05-22 12:21             ` prabindh
2013-01-14 11:37 ` Luca Ceresoli
2013-01-14 11:45   ` Thomas Petazzoni
2013-01-14 12:48     ` Sagaert Johan
2013-01-14 13:10       ` Thomas Petazzoni
2013-01-17  9:03         ` Arnout Vandecappelle [this message]
2013-02-06  9:56 ` Daniel Nyström
2013-02-06 10:04   ` Thomas Petazzoni
2013-02-06 10:12     ` Frédéric COIFFIER
2013-02-06 10:43       ` 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=50F7BE47.6080702@mind.be \
    --to=arnout@mind.be \
    --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