Marco Maggi a écrit :
Let's say that I want this graph of dependencies:
-> GMP module .n ---> GMP adapter .ndll ---> GMP .so
| ^ ^ ^
| | | |
+-> MPFR module .n --> MPFR adapter .ndll --> MPFR .so
| ^ ^ ^
| | | |
+-> MPFI module .n --> MPFI adapter .ndll --> MPFI .so
|
|
application .n
the .ndll files are not installed in the .so usual places
and do not have the canonical name, so how do I link them?
Only Unix only, as long as the ndll are loaded in the good order,
symbold should get resolved without need to link them. On Windows you'll
have to link with the .lib that is built together with the .ndll
Is splitting the adapters into a .so and a stub .ndll the
only solution?
No, you can also statically link the .a code into your .ndll, so you
don't need the .so , that's what is done for instance for mysql.ndll
since there are incompatibilities between runtime libraries versions.
Nicolas
--
Neko : One VM to run them all
(http://nekovm.org)
