If you link vc static lib using gcc, there will be many similar errors
(adding chkstk.obj can solve some problems).
So you'd better link a vc dynamic lib.
On Tue, Aug 30, 2011 at 11:31 PM, Lutz Hayen wrote:
>
> ktiet...@googlemail.com
> > add visual studios chkstk.obj to your link.
>
> Thank you
ktiet...@googlemail.com
> add visual studios chkstk.obj to your link.
Thank you!
This removed the __chkstk errors. Then I discovered that
there were a few similar errors, where
__security_check_cookie was missing. I found that symbol in
runtmchk.lib. I had to remove chkstk.obj again, since t
2011/8/30 Lutz Hayen :
>
> (Reposted to remove 1 line of garbage)
>
> I need to link against a 3rd-party binary-only library that
> was produced with the Visual Studio compiler.
>
> The library is compiled for 64 bit windows (x64). The header
> files are C, not C++, therefore name mangling should n
(Reposted to remove 1 line of garbage)
I need to link against a 3rd-party binary-only library that
was produced with the Visual Studio compiler.
The library is compiled for 64 bit windows (x64). The header
files are C, not C++, therefore name mangling should not be
an issue.
When I compile test
I need to link against a 3rd-party binary-only library that
was produced with the Visual Studio compiler.
All exported symbols The
The library is compiled for 64 bit windows (x64). The header
files are C, not C++, therefore name mangling should not be
an issue.
When I compile test programs wi
