On 11/28/07, <b class="gmail_sendername">Tim Docker</b> &lt;<a href="mailto:timd@macquarie.com.au">timd@macquarie.com.au</a>&gt; wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>&gt; Well I&#39;d say none of the packages I&#39;ve tried, build out of the box...<br><br>I&#39;m not a windows developer, but....<br><br>Is it actually reasonable to expect any cabal packages that depend on<br>external c libraries and headers to build out of the box on windows? How
<br>can cabal find out where those files are, without requiring a config<br>file to be edited?<br><br>Tim</blockquote><div><br>
Tim,<br>
<br>
It is reasonable if you set the LIB and INCLUDE environment variables to
point to the MSYS /usr/local/lib and /usr/local/include directories. Of
course you&#39;ll have to build the c library from source in MSYS/MinGW
for this to work. You&#39;ll also have to manually copy the dll files to a
location in the PATH.<br>
<br>
set LIB=%LIB%;C:\MSYS\1.0\local\lib<br>
set INCLUDE=%INCLUDE%;C:\msys\1.0\local\include<br>
<br>
You can this as a one time change in the Systems control panel. <br>
<br>
If you install the C library from a binary distribution (usually
installed in some arbitrary location on the pc) then the easiest way is
to edit the cabal file.<br>
<br>
Cheers,<br>
<br>
Olivier.<br>
</div></div>