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 2022 at 16:34:06 UTC+1 pepij...@gmail.com wrote: > Hi, > > I'm trying to build my application on Windows and package it as a conda > package. > > After a morning of messing around I managed to build my application in a > Windows VM, but when I submitted the conda recipe, it gives syntax errors > in kj. > > https://github.com/conda-forge/staged-recipes/pull/17515 > > > https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=441167&view=logs&jobId=240f1fee-52bc-5498-a14a-8361bde76ba0&j=240f1fee-52bc-5498-a14a-8361bde76ba0&t=06d62fd2-ab49-5add-9ee5-83b6882d7d2b > > I assume this is something messy with compiler versions and C++ standards. > And it seems capnproto is doing some things in its cmake files to ensure > the library gets built with the correct c++ standard. Yet that doesn't seem > to be happening. > > Is there a recommended way to link to capnproto? I'm currently doing this: > https://github.com/NyanCAD/NgspiceSimServer/blob/main/CMakeLists.txt > > Cheers, > Pepijn > -- 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 capnproto+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/capnproto/4bf7e941-d51a-4e53-b01c-1d119b6fa800n%40googlegroups.com.
