I'm using jskeet's dotnet-protobuf implementation, because we need C# support. I believe it's based on 2.0.1.
Would simply changing FileGenerator::GenerateHeader to output the dllexport_decl in the forward declaration of BuildDescriptors function work? On Oct 21, 1:27 pm, "Kenton Varda" <[EMAIL PROTECTED]> wrote: > I believe this was fixed in 2.0.2. What version are you using? > > On Tue, Oct 21, 2008 at 11:21 AM, <[EMAIL PROTECTED]> wrote: > > > I have a protoc file named UniqueID.proto that is compiled into and > > exported from Communication.dll. > > I have a protoc file named Base.proto that is compiled into and > > exported from Base.dll. > > > Base.proto imports and uses UniqueID.proto. > > Base.dll imports the UniqueID class. > > > Importing and exporting is done via a macro included via the -- > > cpp_out=dllexport_decl= command line option. > > > Heres the problem: > > > Base.pb.cc tries to call protobuf_BuildDesc_UniqueID_2eproto(), which > > doesn't use the macro passed on the command line. The result is a > > linker error. > > > Is it possible to import one .proto file into another when the classes > > they create will be compiled into different dlls? > > > Thanks in advance!! --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/protobuf?hl=en -~----------~----~----~----~------~----~------~--~---
