mldonkey, a multi-networks file-sharing client - Tasks: task #10950, use dynlink for optional features
You are not allowed to post comments on this tracker with your current authentication level.
task #10950: use dynlink for optional features
Submitter: | ygrek <ygrek> | ||
Submitted: | Wed 23 Feb 2011 08:53:04 AM UTC | ||
Category: | Core | Priority: | 5 - Normal |
Status: | None | Assigned to: | ygrek |
Open/Closed: | Open | Should Start On: | Wed 23 Feb 2011 12:00:00 AM UTC |
Should be Finished on: | Wed 23 Feb 2011 12:00:00 AM UTC |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
Powered by Savane 3.13-758e.
Corresponding source code
In order to simplify usage of precompiled binaries on embedded devices where not all required libraries are installed (e.g. http://mldonkey.sourceforge.net/forums/viewtopic.php?p=31272#31272 ) optional features (magic, gd, upnp, etc) should be loaded dynamically so that user can disable them without recompiling. This should be possible with dynlink (for native code since 3.11.0). And so there will be no need to compile several builds (as fabtar did) for distribution, but only one with plugins. Probably this can be done for network plugins too (but more involved I guess).