Hi Johan,<br><br>Originally, that was my intention, to have the user install the library himself,<br>and I have specified the extra-libraries field in the .cabal file. <br><br>However, the problem with hackage not being able to build the package, and<br>
therefore generate documentation, remains. So conversely my question would be<br>if there is any way to get around this?<br><br>Best regards,<br>Max.<br><br><div class="gmail_quote">On Sun, Nov 18, 2012 at 8:21 PM, Johan Tibell <span dir="ltr"><<a href="mailto:johan.tibell@gmail.com" target="_blank">johan.tibell@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Maksymilian,<br>
<br>
Generally I don't recommend that you bundle C libraries with your<br>
Cabal package. On Linux users should get C libraries through their<br>
distribution's package manager. The people who package Cabal packages<br>
for Debian (as Debian packages) can then have the Debian package they<br>
create depend on the C library's package, making sure it gets<br>
installed automatically.<br>
<br>
You can list the library name in an extra-libraries field in your<br>
.cabal file to communicate to users that they need this library<br>
installed. There's a little bit of documentation on the<br>
extra-libraries field in the Cabal User Guide<br>
(<a href="http://www.haskell.org/cabal/users-guide/developing-packages.html#library" target="_blank">http://www.haskell.org/cabal/users-guide/developing-packages.html#library</a>).<br>
<br>
Cheers,<br>
Johan<br>
</blockquote></div><br>