So update on this: it seems the issue was that on windows min/max are
macros that cause extremely weird syntax errors when defining your own
min/max functions.
Upon closer inspection it seems like there wasn't a path escaping issue but
something else weird where the package was built on CI with
On top of this it seems like the CAPNP_GENERATE_CPP cmake macro does not
correctly escape paths (on Windows?). If you'll look at the latest updates
on the PR it seems that a dash in the include path passed to capnproto is
leading to it trying to open the incorrect path.
On Friday, 14 January 20
