-
Notifications
You must be signed in to change notification settings - Fork 40
Problems on Windows #25
Comments
You mentioned it was a complicated setup and I'm sure it was. I would like to try and get it running on windows as well. Could you share some of the steps you took to get the plugin running to this point? |
First thing: building via makefile doesn't work on windows, as it is designed for posix systems.
(Putting it into
Good luck! Try it with the last stable version 1.2.0 so you don't get the error message reported above. |
I have not been able to make this work. For multiple projects on multiple contexts (work, hobby, freelance clients) it would be a very welcome fix. |
The plugin could be useable on Windows if https://code.google.com/p/protobuf/issues/detail?id=399 is fixed in protoc. |
Referenced issue was fixed, so hopefully things are slightly better. Closing as a dup of #10, since we still don't have real Windows support. If anyone wants to step up, I'd love to see some PRs! Or, at least, more concrete issues. |
@jakobr-google please see my latest comment on #10 So far, this appear to generate perfectly correct dart files on Windows. |
After protocolbuffers/protobuf#5105 has come into a release you should be able to pub global activate protoc_plugin, add the pub cache to your path and run protoc --dart_out=.... |
I know that the plugin is not supported on Windows at the moment. But I used it for some month till now and it worked good (except the complicated setup).
But somewhere between the latest stable Dart SDK release (version 1.2.0) and the current dev release (version 1.3.0-dev.3.2, I also tested the version before) the whole thing stopped working. If I run it, the following message is outputted:
Maybe releated to some changes to console IO I saw in the commit log of the Dart repository some days ago?
The text was updated successfully, but these errors were encountered: