I've found that if I don't use STLPort, it works fine. Which is
unfortunate because I need STLPort for Boost to work under WinCE!
Any thoughts on how to get STLPort to work nicely with Protocol


On Oct 30, 10:45 am, PaulH <paul.h...@gmail.com> wrote:
> I'm using Visual Studio 2008 with STLPort 5.2.0 and the Windows Mobile
> 5 R2 SDK to compile protobuf-2.2.0. I was able to compile libprotobuf-
> lite.lib without much difficulty and protoc.exe has no issue compiling
> my proto file:
>     option optimize_for = LITE_RUNTIME;
>     message RCMessage {
>         required int32 version = 1;
>     }
> But, when I try to link against it in a WM5 program, I get linker
> errors (below).
> Can anybody suggest what I may be doing wrong?
> Thanks,
> PaulH
> 1>stlportd.5.2.lib(stlportd.5.2.dll) : error LNK2005: "public: __cdecl
> stlp_std::basic_string<char,class stlp_std::char_traits<char>,class
> stlp_std::allocator<char> >::~basic_string<char,class
> stlp_std::char_traits<char>,class stlp_std::allocator<char> >
> (void)" (??1?$basic_str...@dv?$char_traits@d...@stlp_std@@V?
> $alloca...@d@2@@stlp_std@@q...@xz) already defined in remote.pb.obj
> <snip>
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 
For more options, visit this group at 

Reply via email to