Hi
Following up on a slightly old thread, it seems that the use of
--out-implib is unnecessary for my purposes and generates 50Mb of
.dll.a files. I'm also concerned that the generation of these .dll.a
files may be taking considerable time (in the range of minutes).
I'd like to disable the flags,
I remember that the .dll.a libraries that GCC produces are not always
compatible with MSVC. Sometimes it works if you rename them to .lib
but sometimes it doesn't. It is much more realiable to create .lib
from .def file via some of the MS tools. If GCC can link dynamic
libraries without using the s
On Sat, 2009-05-16 at 11:07 +0100, Neil Mitchell wrote:
> I don't, although having that option wouldn't be a bad thing - having
> a minimal .lib is perfectly reasonable as a default. Having a massive
> .lib seems crazy. (The fact that .lib is named .dll.a isn't too much
> of an issue)
It's possib
>> I've just built a Haskell dll on Windows. As part of the process it
>> generated an 14Mb foo.dll, and a 40Mb foo.dll.a. Looking at the flags
>> passed to ld I see --out-implib=foo.dll.a. What is the purpose of the
>> .a file? What might it be needed for? Is it possible to suppress it?
>
> It loo
On Fri, 2009-05-15 at 15:31 +0100, Neil Mitchell wrote:
> Hi,
>
> I've just built a Haskell dll on Windows. As part of the process it
> generated an 14Mb foo.dll, and a 40Mb foo.dll.a. Looking at the flags
> passed to ld I see --out-implib=foo.dll.a. What is the purpose of the
> .a file? What migh
Hi,
I've just built a Haskell dll on Windows. As part of the process it
generated an 14Mb foo.dll, and a 40Mb foo.dll.a. Looking at the flags
passed to ld I see --out-implib=foo.dll.a. What is the purpose of the
.a file? What might it be needed for? Is it possible to suppress it?
I could easily b
On 22/04/2005, at 10:42 AM, Benjamin Franksen wrote:
I know that ghc cannot produce shared libraries on all systems, but
what about
just linking existing ones (i.e. for ffi code)? Is there a secret
command
line switch for that, or do I have to use the C linker? Is there an
option in
cabal that I
I know that ghc cannot produce shared libraries on all systems, but what about
just linking existing ones (i.e. for ffi code)? Is there a secret command
line switch for that, or do I have to use the C linker? Is there an option in
cabal that I have been missing that could help me?
Cheers
Ben
__
