From: Carsten Schoenert <c.schoenert@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] directfb: bumping version to 1.6.3
Date: Sun, 10 Mar 2013 17:50:37 +0100 [thread overview]
Message-ID: <513CB9DD.2050103@googlemail.com> (raw)
In-Reply-To: <20130310113224.4e3dbb2a@skate>
Hello Thomas,
Am 10.03.2013 11:32, schrieb Thomas Petazzoni:
> This looks good. However, we have a number of packages that depend or
> can use DirectFB: cairo, directfb-examples, libecore, libevas, libgtk2,
> links, lite, gst-plugins-bad, opencv, qt, sawman, sdl, webkit. Did you
> test if those still build after this DirectFB bump? I have no idea if
> the DirectFB bump from 1.4.x to 1.6.x is a major bump (like with API
> breakage) or a minor bump. Depending on that, some testing of the
> packages using DirectFB would be needed, or not.
I have greped which packages depending direct on the directfb package,
this aren't much, I was a little bit surprised and suspected more packages.
> $ git grep -n "depends on BR2_PACKAGE_DIRECTFB"
> package/directfb-examples/Config.in:3: depends on BR2_PACKAGE_DIRECTFB
> ... # more hits on directfb-exables
I tested the directfb-examples, this package has to be bumped. This I
have successful tested and prepared three patches here.
> package/divine/Config.in:3: depends on BR2_PACKAGE_DIRECTFB
Already done in one of my previous patches.
> package/efl/libecore/Config.in:15: depends on BR2_PACKAGE_DIRECTFB
Successful builded.
> package/efl/libevas/Config.in:56: depends on BR2_PACKAGE_DIRECTFB
Successful builded with most of the options (expect OpenGL related stuff).
> package/lite/Config.in:3: depends on BR2_PACKAGE_DIRECTFB
Works perfect, the version is still the current version.
> package/qt/Config.gfx.in:23: depends on BR2_PACKAGE_DIRECTFB
This I will not test, to big the QT beast. :)
> package/sawman/Config.in:3: depends on BR2_PACKAGE_DIRECTFB
Sawan must also bumped to the current version, locally successful done
and builded. Also prepared a patch.
> package/sdl/Config.in:18: depends on BR2_PACKAGE_DIRECTFB
SDL works successful with the new directfb version.
In summary it looks good.
So hopefully I will post later a new patch series.
Regards
Carsten
next prev parent reply other threads:[~2013-03-10 16:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 9:47 [Buildroot] [PATCH 0/0] Updating directfb and divine Carsten Schoenert
2013-03-10 9:47 ` [Buildroot] [PATCH 1/4] directfb: bumping version to 1.6.3 Carsten Schoenert
2013-03-10 10:32 ` Thomas Petazzoni
2013-03-10 12:34 ` Carsten Schoenert
2013-03-17 13:59 ` Carsten Schoenert
2013-03-21 6:56 ` Arnout Vandecappelle
2013-03-21 18:06 ` Carsten Schoenert
2013-03-21 19:13 ` Thomas Petazzoni
2013-04-02 21:56 ` Carsten Schoenert
2013-03-10 16:50 ` Carsten Schoenert [this message]
2013-03-10 17:25 ` Thomas Petazzoni
2013-03-10 9:47 ` [Buildroot] [PATCH 2/4] divine: " Carsten Schoenert
2013-03-10 9:47 ` [Buildroot] [PATCH 3/4] directfb: expanding the help strings Carsten Schoenert
2013-03-10 10:27 ` Thomas Petazzoni
2013-03-10 12:21 ` Carsten Schoenert
2013-03-10 13:13 ` Thomas Petazzoni
2013-03-10 9:47 ` [Buildroot] [PATCH 4/4] directfb: fixing typo in variables Carsten Schoenert
2013-03-10 10:25 ` Thomas Petazzoni
2013-03-10 12:23 ` Carsten Schoenert
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=513CB9DD.2050103@googlemail.com \
--to=c.schoenert@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