[riot-devel] using the native-port for development
martin.landsmann at haw-hamburg.de
Tue May 14 18:49:48 CEST 2013
Dear RIOT developers,
we are currently testing out to develop with the native port of RIOT
which is awesome compared to debugging and dealing with plain sensor-nodes and evaluation platforms.
We figured out that the resulting elf binary using the native port always links to 4 system .so files.
librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xb76f6000)
libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xb754c000)
libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xb7530000)
(In case of an ARM build, say msba2, no linked resources are in use.)
I would like to ask if this is a known behaviour and if there is a way to isolate the native .elf completely from system dependencies?
More information about the devel