rtems dynamic loading with waf

[Saeed Ehteshamifar]

On Thu, Dec 29, 2016 at 9:52 AM, Chris Johns <chrisj at rtems.org> wrote:

> On 28/12/16 9:36 pm, Saeed Ehteshamifar wrote:
> > Dear Xuelin,
> >
> > I share the pointers I emailed you here. Maybe it'd be useful for
> > someone else too.
> > Instructions on how to build a DL app via WAF can be found at:
> > http://rtems-fi.blogspot.com/2016/08/dynamic-linking-in-rtems.html
>
> The blog post is not correct about loading being restricted due to
> transferring object files on the fly. RTEMS will load any available obj
> file and object files do not need to be bound into the base image using
> tar, they just need to be available in a suitable file system. The
> examples and tests bind the object files into the base image because we
> cannot assume available media on a target, eg a simulator. A target with
> a file system such as JFFS and networking could be updated externally
> and the object files loaded from the JFFS file system.
>
Thanks. I updated the blog accordingly.


> Disclaimer: An "unresolved external" error was encountered at run-time,
> > after building the DL app via the above instructions.
>
> The shell command should be able to print a list of unresolved symbols.
>
> > The link also encompasses instructions on how to build a DL app via OMK,
> > as an alternative to WAF. The OMK DL app ran without an error.
> >
> > It'd be nice if you, or anyone who successfully builds a DL app via WAF,
> > share the code/instructions here because AFAIK there's no such example
> > in the RTEMS repository/wiki.
>
> The following is the waf build script I used to develop libdl.
>
> https://git.rtems.org/chrisj/rtl.git/tree/wscript
>
> The libdl support and building for it is complicated and there is a wide
> of things that are possible. Good documentation is needed and something
> I would like to see exist.
>
I hope I can start it in the close future!


>
> Chris
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20161229/2a15dfca/attachment-0002.html>