Embedded Linux Development Kit (ELDK) = software development environment
for Embedded and Real-Time Systems:
- Cross Development Tools (Compiler, Assembler, Linker
etc.) to develop software for the target system.
- Native tools (Shell, commands and libraries) that will
run on the target system up to and including graphical
application frameworks like the X Window System and GNOME Mobile.
- Firmware that can easily be ported to new boards and
processors.
- Linux kernel including all device drivers, board-support
functions etc.
- Xenomai - Extension of the
Linux kernel for systems with hard real-time requirements
- RFSB (Root File System Builder) as base
to build run-time environments for your embedded
systems.
- Integration into popular IDEs (support for Eclipse etc.)
- Free Software with complete source code under GPL and other Open Source licenses.
- ELDK shall be available for free (free download).
- Full source code shall be provided: The complete source
code of the ELDK including all build tools, installation
utilities etc. shall be available for free.
- Installation and use of the ELDK shall not require
super-user privileges: every user shall be able to install the ELDK
without having to ask a system administrator for
help.
- The ELDK shall be self-contained: everything installs into a
single directory; no files get installed or modified in
the host file system tree outside this directory.
- ELDK shall be flexible: it shall be possible to use the same installation
of ELDK for many different projects.
- ELDK shall be efficient: it must be possible to rebuild everything from the source code,
but it shall be sufficient to do this only once, and then use the built binaries and images
without need for rebuild for normal development work.
- ELDK shall support customization: it shall be possible to adapt the ELDK in such a way that
it can be used by the end customer as software production environment for his projects.
- Multiple installations can co-exist: It shall be possible to
install several independent instances of the ELDK
on the same host system (e.g. different releases or different targets).
- Auto-selection of header files and Libraries: the ELDK shall
make it easy to build target software or to use existing
Makefiles; the tools shall make sure that the
correct versions of target header files and system
libraries will get selected automatically.
- ELDK shall be suitable for professional use and meet typical
industrial requirements like strict versioning, exact
reproducibility, updates and bug fixes, etc.
- ELDK shall be multi-platform: we need to support at least
ARM, MIPS and Power Architecture® - x86 support is welcome,
too. All supported architectures shall use the same tools and
provide a homogeneous look and feel.
