Hello, recently, in my play, I ran afoul of the Machinekit-HAL symbol visibility mechanism, where the RTAPI symbols must be post-processed in the output ELF by comparing sections and deleting symbols not defined as an EXPORT_SYMBOL and also the explicit denial of rtapi_app being linked as a -export-dynamic.
(Point: I presume that the userspace RT threads focus is design feature of Machinekit. Not something which happened in the passing.) I plus/minus do get why the symbol isolation is needed. But why was this form used over own linker namespaces with run-time exported symbols to few important functions? And how to best "export" few symbols from rtapi_app to other modules given that rtapi_app cannot export any symbols? The best thing I came up with is to create shared library which will be linked both by rtapi_app and given module, given the fact that all live in one linker namespace. Thanks Cern. -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/Ltg5hHg--3-1%40tuta.io.
