Difference between revisions of "Linux"
(→Framebuffer) |
|||
| Line 5: | Line 5: | ||
== Framebuffer == | == Framebuffer == | ||
| − | The Linux | + | The framebuffer driver can be used to run µGFX on embedded Linux systems that don't run X or a desktop environment. |
<syntaxhighlight lang=make> | <syntaxhighlight lang=make> | ||
include $(GFXLIB)/boards/base/Linux-Framebuffer/board.mk | include $(GFXLIB)/boards/base/Linux-Framebuffer/board.mk | ||
</syntaxhighlight> | </syntaxhighlight> | ||
| + | |||
| + | === Dependencies === | ||
| + | There are no dependencies to use the Linux framebuffer driver. However, the Linux kernel must have been compiled with framebuffer support enabled. | ||
=== Makefile === | === Makefile === | ||
Revision as of 11:39, 15 August 2016
µGFX runs natively on any Linux system. The SDL and X drivers can be used to compile a native Linux desktop application. This is especially useful during the development process as the entire µGFX application can be developed and tested without flashing the target microcontroller every time. The Framebuffer driver is useful to use µGFX on embedded Linux systems that don't run X or a full Desktop environment.
Contents
SDL
Using the SDL driver is the recommended way of running µGFX inside a Linux system with a desktop environment.
Framebuffer
The framebuffer driver can be used to run µGFX on embedded Linux systems that don't run X or a desktop environment.
include $(GFXLIB)/boards/base/Linux-Framebuffer/board.mk
Dependencies
There are no dependencies to use the Linux framebuffer driver. However, the Linux kernel must have been compiled with framebuffer support enabled.
Makefile
A ready-to-use Makefile to compile a native uGFX Linux application can be found under /boards/base/Linux/example/.
X
Using the X driver is not recommended. It's deprecated and an old relic that is kept in the µGFX library as a reference for examples and for systems that are incapable of running SDL. It is STRONGLY recommended to use the SDL driver instead (see above).
The performance of the resulting program is very bad because the X driver just uses setPixel() and doesn't take any advantage of area blitting or double buffering.
