search

huwq007 / protobuf-dt

Automatically exported from code.google.com/p/protobuf-dt
0 stars 0 forks source link

Auto-Compiler problem in Windows #205

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Protoc.exe install path:
D:\Develop\protobuf-2.4.1\protoc.exe

2. Open Compile .proto files on save

3. set 【use protoc in】 option:
D:\Develop\protobuf-2.4.1\protoc.exe

4. set 【descriptor.proto location】option:
D:\Develop\protobuf-2.4.1\src\google\protobuf\descriptor.proto

5. use option 【Generate java】

What is the expected output? What do you see instead?
console output:
[command] D:\Develop\protobuf-2.4.1\protoc.exe 
--proto_path=D:\Source\Android\MgyunService\test.proto 
--proto_path=D:\Develop\protobuf-2.4.1\src 
--java_out=D:\Source\Android\MgyunService\src-protobuf 
D:\Source\Android\MgyunService\test.proto
[protoc]  libprotobuf WARNING google/protobuf/compiler/importer.cc:433] Read 
access is denied for file: D:/Develop/protobuf-2.4.1/src/
[protoc]  : File not found.

What version of the product are you using? On what operating system?
Windows 7 64bit
Eclipse 3.7
Protocol Buffer Editor 1.2.2.201202070201

Please provide any additional information below.
I use this command Generate ok:
D:\Develop\protobuf-2.4.1\protoc.exe 
--proto_path=D:\Source\Android\MgyunService\ 
--java_out=D:\Source\Android\MgyunService\src-gen 
D:\Source\Android\MgyunService\test.proto

Original issue reported on code.google.com by daviyang35 on 25 Feb 2012 at 11:58

GoogleCodeExporter commented 8 years ago 
Hmm...I'm guessing, from the provided output, that we are not using the file 
separator from the OS. I'll investigate further.

Original comment by alr...@google.com on 2 Mar 2012 at 6:01

GoogleCodeExporter commented 8 years ago 
I think this might be a duplicate of Issue 204. I'll keep looking into this.

Original comment by alr...@google.com on 2 Mar 2012 at 6:31

GoogleCodeExporter commented 8 years ago 
I was able to reproduce it in Windows.

Original comment by alr...@google.com on 3 Mar 2012 at 7:21

GoogleCodeExporter commented 8 years ago

Original comment by alr...@google.com on 3 Mar 2012 at 9:35

GoogleCodeExporter commented 8 years ago 
Fixing Issue 203 fixed this issue as well (luckily).

Changes made: r48452a6cad7f

Original comment by alr...@google.com on 4 Mar 2012 at 3:48

GoogleCodeExporter commented 8 years ago 
I'm having the exact same problem on my Linux system. The --proto_path is 
pointing to the .proto file itself and not it's containing directory. I'm using 
protobuf-dt 1.2.3.

Original comment by njdo...@gmail.com on 23 Mar 2012 at 8:30

GoogleCodeExporter commented 8 years ago 
Reopened the bug to investigate further.

Original comment by alr...@google.com on 25 Mar 2012 at 2:53

GoogleCodeExporter commented 8 years ago 
I tested protoc integration and it worked OK. I have a simple .proto file that 
has a couple of messages and imports descriptor.proto.

Please provide instructions on how to reproduce the issue (it would be great if 
you could provide an Eclipse project that reproduces the issue though)

Thanks!

Original comment by alr...@google.com on 25 Mar 2012 at 10:50

GoogleCodeExporter commented 8 years ago 
I've created the most trivial of test cases and attached the Eclipse project.

I get this output:
[command] /home/njdoyle/Prefix/bin/protoc 
--proto_path=/home/njdoyle/Work/Workspace/ProtobufTest/Test.proto 
--java_out=/home/njdoyle/Work/Workspace/ProtobufTest/src-gen 
/home/njdoyle/Work/Workspace/ProtobufTest/Test.proto
[protoc]  : File not found.

I'm using:
Ubuntu 11.04
Eclipse 3.7.0
Protobuf-dt 1.2.3
IBM J9 Java Virtual Machine 1.7.0

Original comment by njdo...@gmail.com on 26 Mar 2012 at 4:15

Attachments:

GoogleCodeExporter commented 8 years ago 
Great! thanks so much. I can see what the issue is.

Original comment by alr...@google.com on 28 Mar 2012 at 8:38

GoogleCodeExporter commented 8 years ago 
r065387dc2d61

Original comment by alr...@google.com on 29 Mar 2012 at 6:40