Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Trapanese <marcotrapanese@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Help about gstreamer h264 in buildroot
Date: Sat, 21 Jun 2014 15:23:35 +0200	[thread overview]
Message-ID: <53A58757.8030701@gmail.com> (raw)
In-Reply-To: <20140621150459.267bce66@free-electrons.com>

Il 21/06/2014 15:04, Thomas Petazzoni ha scritto:
> I don't confirm anything, it just didn't build here, with the error 
> messages that I've posted. 

Ok, you confirm it doesn't build there. I confirm it doesn't build here.

> You shouldn't try to "skip around", but instead you should help us to 
> _fix_ those issues. The support for Qt5+OpenGL is still fairly, and 
> since there are multiple OpenGL implementation, generally one for each 
> platform, we haven't yet tested and fixed all the possible 
> combinations. It is thanks to bug reports provided by users like you 
> that we can progressively fix those issues, and provide a build system 
> that is more and more capable to build all configurations correctly 
> out-of-the-box. Best regards, Thomas 

I understand your point-of-view.
I hope you also understand the frustration of a normal user which try to 
configure its own embedded system.

In the website of buildroot I read:

"Is very easy to set up, thanks to its menuconfig, gconfig and xconfig 
configuration interfaces, familiar to all embedded Linux developers. 
Building a basic embedded Linux system with Buildroot typically takes 
15-30 minutes."

I never had a working buildroot environment since several months! Of 
course I know I'm not an expert so I cannot fix the bugs by myself.
I'm talking about a standard embedded systems (i.MX6 or RPi) with very 
common packages (Qt5, gstreamer).

I also understand no charge is required and in fact I don't expect 
anything from the buildroot staff! But for a user it's not an option to 
delay for days or weeks a project because buildroot doesn't build.

So I'm just wondering if it is possible to know which combination of 
kernel/buildroot version leads to a working environment with basic 
packages. For my current project based upon RPi I need only:

- common utility: ssh (dropbear or openssh), lighttpd, etc (no problem 
here!)
- Qt5 (all modules, egl platform)
- gstreamer with mp3, mp4 h264 and qtmultimedia support

By the way, I don't need Qt5.3, I could use 5.2 as well.

Best regards
Marco

  reply	other threads:[~2014-06-21 13:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-14  9:19 [Buildroot] Help about gstreamer h264 in buildroot Marco Trapanese
2014-06-14 12:14 ` Thomas Petazzoni
2014-06-14 19:50   ` Marco Trapanese
2014-06-14 22:34     ` Thomas Petazzoni
2014-06-17 12:54       ` Marco Trapanese
2014-06-17 13:18         ` Thomas Petazzoni
2014-06-21 11:04   ` Marco Trapanese
2014-06-21 13:04     ` Thomas Petazzoni
2014-06-21 13:23       ` Marco Trapanese [this message]
2014-06-21 16:23         ` Marco Trapanese
2014-06-18 23:13 ` Arnout Vandecappelle

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=53A58757.8030701@gmail.com \
    --to=marcotrapanese@gmail.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