Oh this is going to be a fun one. If it passes on the first run, I'll be impressed :-)

Any progress? Would be great to have Windows support.

Finally getting around to trying this out on an actual Windows PC and.... it passes, all green.

When installing git for Windows, it did ask me about line ending conventions. I configured it to checkout "as is" and push "as is" (e.g. don't attempt to do any LF-> CRLF -> LF conversions/mangling to accommodate dumb Windows tools that expect CRLF). And it passed all tests first try.

So I am pretty sure that the build failure, which indicates a line ending issue, is because the Travis CI machine that was running the build was configured to convert line endings on checkout. So the test files had different line endings and therefore some of the line endings and source position information in source code info was different than expected (the expectations are all based on the files "as is" with simple LF line endings).

I still need to re-base this PR and update it to have Circle CI run the tests on Windows. But one thing that is missing is a test file that deliberately has Windows-style line endings, to make sure that things like source info and comments emitted by protoparse match the behavior of running protoc on Windows.

But one thing that is missing is a test file that deliberately has Windows-style line endings, to make sure that things like source info and comments emitted by protoparse match the behavior of running protoc on Windows.

I'll have to deal with this part later. For now, the fix in the first commit (combined with turning off crlf conversion in git in CI) gets the build green. So this seems like a valuable partial, so that Windows users are mostly able to make use of this repo.

@rogchap, apologies for the long delay. Do take a look at latest master and file a new issue if you see something else that is still messed up on Windows.