Hi all! I'm excited about better MS toolchain support for Cap'n Proto. I'm curious, Harris - have you experimented with using Appveyor for automated testing on Windows? It seems like one difficulty we (the Cap'n Proto community) might run into is that the Sandstorm.io build boxes don't support Windows, so we might regress on the Windows support.
It'd be nice if there were a way for you to sign up with Appveyor and have that service automatically test Cap'n Proto changes for Windows compatibility, even if just on your fork, though I would prefer it to work on the main repo as well, but I know I'll have to convince Kenton of that. :-) Thanks for working so much on VS2015 support! On Fri, May 20, 2016 at 10:04 AM, Harris Hancock <[email protected]> wrote: > Hi Kenton, > > Thanks for merging my lite mode PR. As I mentioned there, I think a good > next step in the Microsoft world will be to get the capnp tools (compiler > and plugins) built using MSVC. That should remove the requirement to build > with MinGW separately first, and thus lower the barrier of entry for MSVC > devs. I should be able to put together a PR for that in a few days, as it > should mostly just be more cherry picking from my earlier work. > > After that, the distance between master and VS2015-compiles-everything > should be significantly smaller, and easier to assess. > > Also, thanks for your patience! > > Harris > > -- > You received this message because you are subscribed to the Google Groups > "Cap'n Proto" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > Visit this group at https://groups.google.com/group/capnproto. > -- You received this message because you are subscribed to the Google Groups "Cap'n Proto" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/capnproto.
