4. Host Computer

RTEMS applications are developed using cross-development tools running on a development computer, more often called the host computer. These are typically your desktop machine or a special build server. All RTEMS tools and runtime libraries are built from source on your host machine. The RTEMS Project does not maintain binary builds of the tools. This differs to what you normally experience with host operating systems however this approach works well. RTEMS is not a host operating system and it is not a distrbution. Deploying binary packages for every possible host operating system is too big a task for the RTEMS Project and it is not a good use of core developer time. Their time is better spent making RTEMS better and faster.

The RTEMS Project’s aim is to give you complete freedom to decide on the languages used in your project, which version control system, and the build system for your application.

The rule for selecting a computer for a developer is more is better but we do understand there are limits. Projects set up different configurations, some have a development machine per developer while others set up a tightly controlled central build server. RTEMS Ecosystem is flexible and lets you engineer a development environment that suites you. The basic specs are:

• Multicore processor

• 8G bytes RAM

• 256G harddisk

RTEMS makes no demands on graphics.

If you are using a VM or your host computer is not a fast modern machine do not be concerned. The tools may take longer to build than faster hardware however building tools is something you do once. Once the tools and RTEMS are built all your time can be spent writing and developing your application. It may take longer than an hour for the ARM architecture and with all BSPs it can be many hours.

• 4.1. Python
  • 4.1.1. Virtual Environment
  • 4.1.2. Symbolic Link
  • 4.1.3. Directly Invoking Python
• 4.2. Host Operating Systems
• 4.3. POSIX Hosts
  • 4.3.1. Root Access
  • 4.3.2. Linux
    • 4.3.2.1. ArchLinux
    • 4.3.2.2. CentOS
    • 4.3.2.3. Fedora
    • 4.3.2.4. Raspbian
    • 4.3.2.5. Ubuntu
    • 4.3.2.6. Linux Mint
    • 4.3.2.7. openSUSE
  • 4.3.3. FreeBSD
  • 4.3.4. NetBSD
• 4.4. Apple macOS
  • 4.4.1. Python
  • 4.4.2. Sonoma
  • 4.4.3. Ventura
  • 4.4.4. Monterey
  • 4.4.5. Catalina
  • 4.4.6. Sierra
  • 4.4.7. Mavericks
• 4.5. Microsoft Windows
  • 4.5.1. Windows Path Length
  • 4.5.2. Windows Spaces In Paths
  • 4.5.3. Parallel Builds with Make
  • 4.5.4. POSIX Support
  • 4.5.5. Python
  • 4.5.6. MSYS2
  • 4.5.7. Cygwin