The L4 Environment, short L4Env, is a programming environment for applications that should run on the L4.Fiasco kernel. L4Env was developed to provide basic building blocks such as a C library or memory management.
Prior to L4Env application developer wrote their software to use the basic mechanisms provided by the L4 microkernel. These included software to provide functions, such as malloc, free, printf, etc. Because, the implementations were mostly similar and application developers should be writing applications, instead of support libraries, these software was combined into a programming environment.
Now that the L4Env provided basic functionality, more applications and more sophisticated software could be made run on L4.
L4Env might not be perfect and contain all the functionality someone might require, it has proven to be a stable basis. And, as demand requires, it grows to include more functionality.
What it provides
- L4 Threads: thread startup and termination, thread-local storage
- Task server / hierarchical task interface: task startup and termination
- Dataspace Managers: memory management (pager, malloc, free)
- System bootup services (bootstrap, roottask, etc.)
- Names: basic name service
- Dynamic application startup (loader, ldso, tftp, bmodfs)
- C library (port of a subset of the uClibc)
More complex services are provided in additional packages:
- L4VFS: virtual console (vt100) support, higher level name service, basic file server, many more
- ports of different graphic libraries like Qt3
- console system: l4con
- basic window manager: Nitpicker, DOpE
- signal: POSIX signalling mechanism
What it does not provide
- pthread library
- full file system support
- a full POSIX system
- L4Env manuals (generated from current SVN sources)