J
Joske
Hi,
I'm having a similar problem as Scott. A static library
with managed C++ functions fails to link in.
See http://groups.google.be/groups?q=managed+C+%
2B+static+library&start=10&hl=en&lr=&ie=UTF-8&oe=UTF-
8&selm=uXE2ZMiqDHA.2644%40TK2MSFTNGP09.phx.gbl&rnum=14
(BTW why can I find scott's post with Google and not using
the msdn web-interface? It seems to have vanished)
I've created a static library using VC++ 7.0. I builds
fine, but when I try to use it the linker complains about
unresolved externals. I've traced the linker progress to
make sure that the .lib file was found. Curiuously free
functions are found, while class member functions are not.
Is this a compiler problem? Something with the name
mangling? I've dumped the contents of the produced lib
using dumpbin and it appears that the symbols are in there.
Any help is appreciated,
Joske
I'm having a similar problem as Scott. A static library
with managed C++ functions fails to link in.
See http://groups.google.be/groups?q=managed+C+%
2B+static+library&start=10&hl=en&lr=&ie=UTF-8&oe=UTF-
8&selm=uXE2ZMiqDHA.2644%40TK2MSFTNGP09.phx.gbl&rnum=14
(BTW why can I find scott's post with Google and not using
the msdn web-interface? It seems to have vanished)
I've created a static library using VC++ 7.0. I builds
fine, but when I try to use it the linker complains about
unresolved externals. I've traced the linker progress to
make sure that the .lib file was found. Curiuously free
functions are found, while class member functions are not.
Is this a compiler problem? Something with the name
mangling? I've dumped the contents of the produced lib
using dumpbin and it appears that the symbols are in there.
Any help is appreciated,
Joske