Difference between revisions of "DirectFB"
m (Change to a more specific category.)
(Template:i18n is deprecated, use interlanguage links, see Help talk:I18n#"Dummy" interlanguage links and deprecation of Template:i18n)
|(One intermediate revision by the same user not shown)|
|Line 1:||Line 1:|
== Overview ==
== Overview ==
Revision as of 16:17, 13 June 2012
DirectFB stands for Direct Frame Buffer. It is a software library for GNU/Linux/Unix-based operating systems with a small memory footprint that provides graphics acceleration, input device handling and abstraction layer, and integrated windowing system with support for translucent windows and multiple display layers on top of the Linux framebuffer without requiring any kernel modifications. DirectFB is free software licensed under the terms of the GNU Lesser General Public License (LGPL).
With the default build of the DirectFB library, only one DirectFB application may be running. However you have the option to use the multi application core of DirectFB along with linux-fusion which allows multiple DirectFB applications to run at the same time within a session.
DirectFB's frameworks for building apps on top of it is somewhat weak and needs work. It lacks of a real Window Manager (WM). The recently released WM SaWMan and its "testman" could be a good starting point, although it is not fully functional. see http://directfb.org/wiki/index.php/The_DirectFB_Desktop. Disko however, that can use DirectFB or even fbdev directly, may help rectify this situation.
DirectFB 2.0: Universal Framework Support. The main goal of the new universal framework is to make the core of DirectFB an api agnostic library. Sort of a OS kernel for the gpu. To reach this goal some code will be moved out of the core into modules and the internal core api will be exposed as a system programming api for library writers. see http://directfb.org/wiki/index.php/DirectFB_2.0:_Universal_Framework_Support
Mandatory are - libc - libpthread - libm - libdl
For regenerating autofoo (./autogen.sh or autoreconf) - autoconf - automake - libtool - pkg-config
Optionally, depending on the configuration you want:
FBDev (when using the kernel frame buffer backend (somewhat the goal of at least the initial directfb) the fbdev install/setup needs explaining, eg: /dev/fb0 .. ) - Linux kernel 2.2.x or newer with working frame buffer device (check /proc/fb) for the fbdev system.
SDL - libSDL (Simple Direct Media Layer) for the sdl system.
X11 - libX11 (X11 client library) for the X11 system (libx11-dev and libxext-dev packages).
The following libraries are optional, but important (Debian package names):
Fonts - libfreetype6-dev for TrueType and other fonts
Images - libjpeg-dev for Joint Picture Expert Group images - libpng-dev for Portable Network Graphics
Extra - zlib1g-dev for compressed screenshot support (also needed by libpng)
If you are planning to run multiple DirectFB applications simultaneously, you need to build the linux-fusion kernel module.
You can now also build and install DirectFB-examples which contain some example applications and some benchmarks.
SawMan was the original WM and has been stated to prove itself sufficient to get things going. Lite is a qui toolkit targeted to applicatoin developers. Disko however would seem to provide a much better higher level platform with which a general and rather flexible (user space definable) WM, as an application, and (actual) applications can be defined. In any case all three are suggested if you want to futz around with DirectFB.
Installation Step by Step
(better a link to a SawMan page)
(better a link to a Lite page)
(better a link to a disko page)
- kernel frame buffer help/tips