[protobuf] Re: Issue 459 in protobuf: Wildcard input path for proto files does not work in 2.5.0rc1

2013-08-14 Thread protobuf
Comment #8 on issue 459 by paul.bax...@googlemail.com: Wildcard input path for proto files does not work in 2.5.0rc1 http://code.google.com/p/protobuf/issues/detail?id=459 Confirmed that adding /link setargv.obj in protoc works on vs2008 sp1 - any chance this can be merged into next

[protobuf] Re: Issue 459 in protobuf: Wildcard input path for proto files does not work in 2.5.0rc1

2013-02-18 Thread protobuf
Updates: Status: WorkingAsIntended Comment #4 on issue 459 by xiaof...@google.com: Wildcard input path for proto files does not work in 2.5.0rc1 http://code.google.com/p/protobuf/issues/detail?id=459 Protocol compiler is not supposed to expand wildcards. I believe the problem has

[protobuf] Re: Issue 459 in protobuf: Wildcard input path for proto files does not work in 2.5.0rc1

2013-02-18 Thread protobuf
Comment #5 on issue 459 by askl...@gmail.com: Wildcard input path for proto files does not work in 2.5.0rc1 http://code.google.com/p/protobuf/issues/detail?id=459 Protocol compiler is not supposed to expand wildcards. If that's the case, then there is a bug. The available Protobuf compiler

[protobuf] Re: Issue 459 in protobuf: Wildcard input path for proto files does not work in 2.5.0rc1

2013-02-18 Thread protobuf
Comment #6 on issue 459 by liuj...@google.com: Wildcard input path for proto files does not work in 2.5.0rc1 http://code.google.com/p/protobuf/issues/detail?id=459 The win32 binary is compiled using MinGW32 (statically linked with MinGW32 lib). I think the MinGW32 lib handles wildcast

[protobuf] Re: Issue 459 in protobuf: Wildcard input path for proto files does not work in 2.5.0rc1

2013-02-18 Thread protobuf
Comment #7 on issue 459 by askl...@gmail.com: Wildcard input path for proto files does not work in 2.5.0rc1 http://code.google.com/p/protobuf/issues/detail?id=459 In that case, the Visual Studio solution included in the protobuf source code has a bug. You need to add /link setargv.obj in

[protobuf] Re: Issue 459 in protobuf: Wildcard input path for proto files does not work in 2.5.0rc1

2013-02-16 Thread protobuf
Comment #2 on issue 459 by askl...@gmail.com: Wildcard input path for proto files does not work in 2.5.0rc1 http://code.google.com/p/protobuf/issues/detail?id=459 So it appears that this problem has nothing to do with source code, but compiler versions. I tried compiling 2.4.0, 2.4.1,

[protobuf] Re: Issue 459 in protobuf: Wildcard input path for proto files does not work in 2.5.0rc1

2013-02-16 Thread protobuf
Comment #3 on issue 459 by askl...@gmail.com: Wildcard input path for proto files does not work in 2.5.0rc1 http://code.google.com/p/protobuf/issues/detail?id=459 Alright, finally found the answer after a wild goose chase. In Unix, path expansion has nothing to do with code, but everything

[protobuf] Re: Issue 459 in protobuf: Wildcard input path for proto files does not work in 2.5.0rc1

2013-02-12 Thread protobuf
Comment #1 on issue 459 by askl...@gmail.com: Wildcard input path for proto files does not work in 2.5.0rc1 http://code.google.com/p/protobuf/issues/detail?id=459 More information: 2.4.0a appears to work. 2.4.1 does not work. 2.5.0rc1 does not work. Appears to be broken somewhere between