[Gc] VS2005 .sln and .vcproj file

Giles Payne gilespayne at gmail.com
Tue Feb 1 18:16:13 PST 2011

Hi Ivan,

The problem relates to generating a manifest file and embedding it as a
resource inside the binary - you certainly could add steps inside the
makefile to do that - but it looked like too much effort :)

Not sure what is different about your VS2010/NT_X64_THREADS_MAKEFILE combo -
if the resulting DLL has no dependency on msvcrXX.dll then I guess it is
statically linking the standard C library. I did try hacking
NT_THREADS_MAKEFILE to statically link the C library but that caused me
other problems (no functions were being exported)


2011/2/2 Ivan Maidanski <ivmai at mail.ru>

> Hi Giles,
> I tried NT_THREADS_MAKEFILE (which I created from NT_X64_THREADS_MAKEFILE
> replacing X64 to X86) of the latest BDWGC snapshot with VS2010 Express and
> it worked fine. There is no dependency to msvcrXX.dll (and no manifest).
> Is the issue you describe specific to VS2005? Why is it not possible to use
> makefile to solve the problem?
> Tue, 1 Feb 2011 21:41:26 +0900 Giles Payne <gilespayne at gmail.com>:
> > Hi,
> >
> > Recently I tried building libgc for windows with VS2005. I got it to
> build
> > using NT_THREADS_MAKEFILE but the resulting DLL was unusable (anyone
> > interested in why can google "msvcr80.dll manifest" for an explanation.)
> The
> > long and the short of it was I created a .sln and .vcproj file and was
> able
> > to build a usable DLL from them. I'm attaching these files in case they
> are
> > of use to anyone,
> >
> > Thanks,
> >
> > Giles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://napali.hpl.hp.com/pipermail/gc/attachments/20110202/bddb9211/attachment.htm

More information about the Gc mailing list