On Jul 9, 8:54 pm, "Alex Black" <a...@alexblack.ca> wrote:
> Hey Bart, I'm not sure I'm seeing the full details of your situation,
>
> But on windows I compiled a library libprotobuf.lib, and linked to it
> statically, meaning it gets built into the exe (or dll) you're building.
> (I built 2 actually, a release one and a debug one).
That's how it works on Linux. Here's the problems we're having on
Windows. We're building protoc with the mingw compiler system included
in the Qt 4.5.1 SDK. This doesn't generate .lib files, but .la files
and .a files. The .a is a "static archive". When I run 'nm
libprotobuf.a' I get all the typical protobuf function definitions, so
that looks ok.
However, when I try to build my application with -L"path/to/
libprotobuf.a" I get hundreds of linker errors, complaining about
undefined references to any of the google protocol functions.
I'm using the same mingw compiler to build my Qt application, so that
is not the problem.
Anyway, I'm still struggling with this stuff, and since no one at my
company knows anything about C++ on Windows, it's a hassle. So that's
why I just try to circumvent the problem by just linking the object
files directly.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To post to this group, send email to protobuf@googlegroups.com
To unsubscribe from this group, send email to
protobuf+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/protobuf?hl=en
-~----------~----~----~----~------~----~------~--~---
