From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0004224]: DirectFB Makefile does not support 1.0.x / 1.2.x and Examples not supported
Date: Mon, 21 Jul 2008 05:31:32 -0700 [thread overview]
Message-ID: <bc5aaca70c9bb62327fbe30afe158041@busybox.net> (raw)
A NOTE has been added to this issue.
======================================================================
http://busybox.net/bugs/view.php?id=4224
======================================================================
Reported By: daniellaird
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 4224
Category: New Features
Reproducibility: always
Severity: feature
Priority: normal
Status: assigned
======================================================================
Date Submitted: 07-21-2008 05:03 PDT
Last Modified: 07-21-2008 05:31 PDT
======================================================================
Summary: DirectFB Makefile does not support 1.0.x / 1.2.x and
Examples not supported
Description:
DirectFB makefile supports out of date version and does not support the
building of examples.
This patch adds support for 1.0.X and 1.2.x building and DirectFB examples
as well
======================================================================
----------------------------------------------------------------------
Correa - 07-21-08 05:21
----------------------------------------------------------------------
Is there a reason to support multiple versions? If possible, we would
rather avoid having to choose versions and keep the latest one only.
----------------------------------------------------------------------
daniellaird - 07-21-08 05:31
----------------------------------------------------------------------
Yes, The DirectFB API version has moved on. DirectFB 1.2 is the latest
version but some packages will not compile against DirectFB 1.2.
Where I work we are moving to DirectFB 1.2.X but the transition window
means supporting both in the short term.
With a completely new DirectFB (DFB 2.0) being planned for the future that
will will change the API significantly then we will need support for DFB1.X
vs DFB2.X anyway so this change will again be useful then.
I am in no position to move buildroot to 1.2.x series but require support
for it.
This seemed the best option.
Issue History
Date Modified Username Field Change
======================================================================
07-21-08 05:03 daniellaird New Issue
07-21-08 05:03 daniellaird Status new => assigned
07-21-08 05:03 daniellaird Assigned To => buildroot
07-21-08 05:03 daniellaird File Added: directfb_update.patch
07-21-08 05:21 Correa Note Added: 0009874
07-21-08 05:31 daniellaird Note Added: 0009884
======================================================================
next reply other threads:[~2008-07-21 12:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 12:31 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-20 7:24 [Buildroot] [buildroot 0004224]: DirectFB Makefile does not support 1.0.x / 1.2.x and Examples not supported bugs at busybox.net
2008-10-20 7:24 bugs at busybox.net
2008-10-20 7:23 bugs at busybox.net
2008-10-13 16:07 bugs at busybox.net
2008-07-21 12:21 bugs at busybox.net
2008-07-21 12:03 bugs at busybox.net
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=bc5aaca70c9bb62327fbe30afe158041@busybox.net \
--to=bugs@busybox.net \
--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