Using cabal to 'install' a shared library for wxhaskell
dukedave at gmail.com
Tue Jan 3 20:30:15 CET 2012
I have resolved this issue by adding the rpath to the dependent package's
ldOptions , but I'm not particularly happy with it.
My solution was inspired by an old post describing a similar problem with
rpath , was this ever looked at?
On 24 December 2011 01:32, Dave Tapley <dukedave at gmail.com> wrote:
> Hi all,
> I've been working on a new development version of wxhaskell and one of
> my goals was to integrate previous work on using a shared library.
> I'm please to report that I have more-or-less achieved this goal at least
> under Linux, but there is still some cleaning up to do.
> After performing a cabal I end up with a .so file as expected, the only
> problem currently is that now whenever you compile something which uses
> wxhaskell you have to pass in an rpath to the .so in the cabal-dev / local
> / system packages location.
> Obviously this .so somehow needs to end up where the system can find it,
> and I wondered if someone has already (or has ideas about how to) make this
> happen in cabal?
> You can see where I believe it should fit in in the ldconfig function in
>  http://darcsden.com/DukeDave/wxhaskell-dev
>  http://darcsden.com/DukeDave/wxhaskell-dev/browse/wxc/Setup.hs
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Libraries