| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
The DirectFB project is dead upstream for a while and the backend is
deprecated so it is better to drop it and avoid new users to depend on
it and instead to focus in the current technologies for new projects.
This commit removes everything related to the DirectFB support so if
someone wish to revert it locally it can be easily done.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Acked-by: Daiane Angolini <daiane.angolini@freescale.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The OE-Core commit:
commit 8a577fa7cf54db646f4e61f383390054e5f04ca3
Author: Khem Raj <raj.khem@gmail.com>
Date: Tue Sep 8 22:12:46 2015 +0000
directfb: Avoid using VLAs and printf formats
These are not portable features and are flagged by clang
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Broke the directfb build as the new patch has been applied in the .inc
file and was unconditionally being included. The patch was include for
new versions of DirectFB and we ought to avoid including changes from
OE-Core, for this recipe, without notice.
It is likely the patch needs to be ported later for the forked
DirectFB recipe but this is should be done afterwards.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The runtime dependency against libvivante-dfb-mx6 should be specified
in the directfb main package, not in the packagegroup so there is no
risk of it not being right in a customer image.
The other benefit in doing this rework is that the DirectFB 1.7.4
version recipe has no changes and can be immediately removed once
Freescale upgrades the Vivante GPU bindings for DirectFB 1.7.7
support.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Poky master upgraded directfb to 1.7.6 but 3.10.53-1.1.0 GA
release is compatible with directfb 1.7.4.
Signed-off-by: Neena Busireddy <neena.busireddy@freescale.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|