[KIELER-20] Better way to handle native libraries Created: 27/Aug/08 Updated: 09/Jan/09
Resolved:
09/Jan/09
Status:
Project:
Component/s:
Affects
Version/s:
Fix Version/s:
Type:
Reporter:
Resolution:
Labels:
Remaining
Estimate:
Time Spent:
Original
Estimate:
Closed
Kieler
Administration
None
None
New Feature
Hauke Fuhrmann [X]
(Inactive)
Fixed
None
Not Specified
Priority:
Assignee:
Minor
Hauke Fuhrmann [X] (Inactive)
Votes:
0
Not Specified
Not Specified
Description
Find a better way to include native libraries (e.g. GraphViz) to a plugin.

For now it's only done by using absolute path specification by LD_LIBRARY_PATH
parameter to VM
Comments
Comment by Hauke Fuhrmann [X] (Inactive) [ 25/Sep/08 ]
ars, I just put you on cc, don't expect you to do something about it, as it seems not to be trivial.
Comment by Hauke Fuhrmann [X] (Inactive) [ 25/Sep/08 ]
Checking the newsgroups, fragments seems to be used for that:


Create a common plugin for the basic Java code
Create a fragment for that plugin for every platform
o Include native libraries for the platform in its coresponding fragment
o Specify the target OS, WS and ARCH for every fragment
o
Fragment will override certain classes of the common related plugin
Then at startup only the correct matching platform fragment will be loaded
Comment by Hauke Fuhrmann [X] (Inactive) [ 09/Jan/09 ]
Solutions with fragments documented in the wiki:


[Help/EclipseCookbook/NativeCode]
[Projects/KIML/GraphViz]
For Graphviz not appropriate (details see links above). Here will follow a commandline
interface.
Generated at Wed Feb 10 08:39:07 CET 2016 using JIRA 6.4.12#64027sha1:e3691cc1283c0f3cef6d65d3ea82d47743692b57.