On 27/07/2016 19:28, Pavel Pisa wrote:
On Wednesday 27 of July 2016 02:57:06 Chris Johns wrote:
Pavel, thanks for the excellent detail provided. I will try and expand
on a couple of parts being discussed.
You need to link list of symbols to the base executable image
to inform runtime linker
>
> The rtems_waf support (https://git.rtems.org/chrisj/rtems_waf.git/) now
>> provides a simple way to add files via an embedded tar file to an
>> executable. You can:
>
> How can I start using WAF build system? I found
> https://devel.rtems.org/wiki/waf on the wiki but it wasn't helping much.
>
Hello,
Thanks for the answers Pavel, Chris.
You need to link list of symbols to the base executable image
> to inform runtime linker which symbols are available.
I followed your instructions carefully and after building my app, I get an
"untar failed: 1" error. How should I debug this error? My
Pavel, thanks for the excellent detail provided. I will try and expand
on a couple of parts being discussed.
On 27/07/2016 10:00, Pavel Pisa wrote:
On Wednesday 27 of July 2016 01:01:29 Saeed Ehteshamifar wrote:
1. How to generate *tar* array? Since on top of dl-tar.c it's been noted
that
image of RTEMS application which includes IMS initial data in
TAR object
# file, symbol table and objects forming application
arm-rtems4.12-gcc ${CFLAGS1} -Wl,--gc-sections init.o rootfs_tarfile.o
task_1.o appdl-symbol-table.o -L . -lbar -lm -o appdl
This list is highly simplified, but should give some
o
Hello,
Thanks Pavel for your answer. I tried to write an app myself that uses
dynamic loading and I ended up with the following questions:
1. How to generate *tar* array? Since on top of dl-tar.c it's been noted
that it's automatically generated. If I'm not wrong, by making a tar image,
RTEMS
