fae63f4fa9
This patch simplifies the way of how Genode's base libraries are organized. Originally, the base API was implemented in the form of many small libraries such as 'thread', 'env', 'server', etc. Most of them used to consist of only a small number of files. Because those libraries are incorporated in any build, the checking of their inter-dependencies made the build process more verbose than desired. Also, the number of libraries and their roles (core only, non-core only, shared by both core and non-core) were not easy to capture. Hereby, the base libraries have been reduced to the following few libraries: - startup.mk contains the startup code for normal Genode processes. On some platform, core is able to use the library as well. - base-common.mk contains the parts of the base library that are identical by core and non-core processes. - base.mk contains the complete base API implementation for non-core processes Consequently, the 'LIBS' declaration in 'target.mk' files becomes simpler as well. In the most simple case, only the 'base' library must be mentioned. Fixes #18 |
||
|---|---|---|
| .. | ||
| framebuffer_window.h | ||
| main.cc | ||
| README | ||
| services.cc | ||
| services.h | ||
| target.mk | ||
Liquid frame buffer is an implementation of the frame buffer interface running as a client of the Nitpicker GUI server. It supports the following configuration options. The example shows the default values. ! <config> ! ! <!-- enable the animated background, ! valid values or 'on' and 'off' --> ! <animate>on</animate> ! ! <!-- the initial window position and ! size of the virtual frame buffer --> ! <x>400</x> ! <y>270</y> ! <width>500</width> ! <height>400</height> ! ! <!-- set the window title --> ! <title>Liquid Framebuffer</title> ! ! </config> Because Liquid frame buffer creates the virtual frame-buffer window at start time, not at session-creation time, sufficient memory resources must be provided when starting the program. Consequently, the client does not need to donate memory for the frame buffer backing store. Liquid frame buffer supports only one client. If multiple virtual frame buffers are needed, multiple instances of the program should be used.