Remote projects on RT-Druid

Introduction

There are some scenarios in which the board has the processing capabilities for running a full compiler, but it cannot run the Eclipse IDE.
This is the case, for example, of powerful multi-core ARM SoCs running a Linux distribution, using a hypervisor like Jailhouse for running ERIKA alongside Linux.
In such circumstances, having a native compilation of ERIKA on the target could be easier than cross-compiling using a host machine. Unfortunately, the Eclipse IDE requires an x86 platform with a fair amount of resources (in terms of both processing and memory).

This guide, therefore, explains how to set-up Eclipse on a host x86 machine, leaving the compilation process on the target. Handling a remote project can be done manually, of course, by transferring the built files through ftp/scp/rsync or by mounting locally the target filesystem using nfs/sshfs. However, this guide explains how to use the remote project feature of Eclipse which internally relies on the sftp protocol.

Important: since the build process is one on the target the code of ERIKA must be available on the target. Similarly, all tools and the environment variables needed for the building process must be available on the target.

Notes

• Currently, Acceleo is not capable of generating files on top of the Eclipse virtualization.

The generation is therefore done in two steps:

   * Acceleo generates files in a directory within the local workspace: .metadata/.plugins/com.eu.evidence.rtdruid3.oil.cdt.ui/oil_gen
   * RR_druid copies the files from the local to the remote directory (using the Eclipse virtualization)

• Since the