[fpc-devel] "embedded" again

[Michael Schnell]

Hi FPC Experts.

I am doing a project that in the end is supposed to run on a QNAP 219 
NAS. A colleague of mine is doing a similar task, that is supposed to 
run on a Raspberry Pi.

Both these systems run Linux on a decently up to date ARM CPU.

The obvious way to go is to use Lazarus on Windows and/or PC-Linux to 
create and debug the software, and create "functional" objects in 
dedicated units and for testing add "GUI" Units to allow for code 
instrumentation with "internal state" and "simulated actuator" output 
and for "simulated sensors". Moreover there can be "remote control" 
objects for attaching real sensors and actuators. The "GUI-Debug" 
Objects communicate with the functional objects via function calls and 
Events.

When the code seems to work appropriately, the GUI and simulation units 
can be replaced by units that (without needing a GUI) can work in the 
embedded environment. Only a limited amount of final testing needs to be 
done there.


Now the question is how the project should be compiled for the ARM target.

Both systems allow for installing FPC but are not able to (decently) run 
a GUI system for Lazarus.

So the options are either to do cross compiling (with Lazarus) or to 
install FPC on the target and compile the code there.

What is the more viable way ?


BTW. (maybe better handled in the Lazarus Forum): I do know that gdb 
allows for remote debugging vie TCP/IP. So when cross-compiling it 
should be possible to remote-debug the project on the ARM-Target from a 
(Linux) PC using Lazarus. Did anybody test this, yet ?


Thanks for any answers
-Michael