Linking against multiple module libraries

[frozencemetery]

Issue migrated from trac ticket # 5

component: component1 | priority: major | resolution: fixed

2011-09-07 14:00:25: @greghudson created the issue

---

libverto modules can be used as dynamically loaded objects or as directly linked libraries. They export module-specific symbols like verto_libev_default(), but also a fixed-named data symbol verto_module_table. Trying to link against two module libraries (perhaps one by the application and another by a subsidiary library which uses a private event loop) would result in a symbol conflict.

Verbally, Nathaniel has suggested that the module table symbol name will be changed to include the module name. This will require deducing the module name from the pathname in verto.c:do_load_dir().

[frozencemetery]

2011-11-09 14:35:53: @npmccallum changed status from new to closed

[frozencemetery]

2011-11-09 14:35:53: @npmccallum changed resolution from ** to fixed

[frozencemetery]

2011-11-09 14:35:53: @npmccallum commented

---

Fixed in 365972e.