b1ackmai1er

Group: Members
Posts: 115
Joined: June 2005 |
 |
Posted: Sep. 15 2007,15:12 |
 |
Yes, as WDef suggests, adding extensions with libraries is a pain.
If we could have /opt/lib in the library path, install our extensions to /opt/app/bin .. /lib etc and have and put our links to the applications libraries in /opt/lib that would be great.
Or as part of the extension loader, recognise libraries (*.so files) and build the the library links automatically.
Generally, I think DSL should come built in with a toolkit of scripts to assist building extensions.
Cheers Phil
|