- 28 Apr, 2017 15 commits
-
-
Kenton Varda authored
-
Harris Hancock authored
-
Harris Hancock authored
While the VS2015 build no longer depends on the MinGW installation as an external capnp, I think testing the CMake MinGW build on Windows probably remains worthwhile.
-
Harris Hancock authored
This option was only useful when MSVC couldn't build the capnp command line tools, so let's back it out.
-
Harris Hancock authored
The previous solution used hard-coded paths which would have had to be special-cased for multi-configuration generators such as Visual Studio, which put binaries in individual Debug, Release, etc. directories.
-
Harris Hancock authored
-
Kenton Varda authored
-
Harris Hancock authored
MSVC as of VS2015 does not initialize the vtable pointers of constexpr objects, causing nullptr dereferences at runtime. To solve this, we can just convert them to regular const variables with internal (static) linkage. The internal linkage bit is important: as long as they are invisible outside their respective translation units, we do not risk the static initialization order fiasco. If we ever need to reference them outside their translation units, we would need to hide them behind functions (like HeapArrayDisposer::instance()) to keep things safe.
-
Harris Hancock authored
This works around an issue which prevented kj::parse::ref() from compiling.
-
Harris Hancock authored
The fix in ae6b4452 worked for getting the HTTP code building, but was apparently insufficient for the capnp command line tools.
-
Kenton Varda authored
-
Kenton Varda authored
This is currently passing.
-
Kenton Varda authored
This is currently passing.
-
Kenton Varda authored
-
Kenton Varda authored
-
- 27 Apr, 2017 3 commits
-
-
Kenton Varda authored
-
Kenton Varda authored
-
Kenton Varda authored
-
- 26 Apr, 2017 8 commits
-
-
Kenton Varda authored
Add kj-http to cmake build.
-
Kenton Varda authored
-
Harris Hancock authored
-
Harris Hancock authored
-
Kenton Varda authored
Apparently the test has accidentally been using the installed capnp all along.
-
Kenton Varda authored
-
Kenton Varda authored
Fixes #196
-
Kenton Varda authored
Bug fix rollup for 0.6 release
-
- 25 Apr, 2017 14 commits
-
-
Kenton Varda authored
Fixes #212
-
Kenton Varda authored
Specifically, consider: capnp::BuilderFor<capnp::DynamicStruct> capnp::Orphan<capnp::AnyPointer>::getAs<capnp::DynamicStruct>(capnp::StructSchema) Note that `BuilderFor` is a "template using" directive which expands into something more complicated. GCC mangles the symbol as: _ZN5capnp6OrphanINS_10AnyPointerEE5getAsINS_13DynamicStructEEENS_11BuilderFor_IT_Xcl4kindIS6_EEEE4TypeENS_12StructSchemaE Which `c++filt` decodes as: capnp::BuilderFor_<capnp::DynamicStruct, (kind<capnp::DynamicStruct>)()>::Type capnp::Orphan<capnp::AnyPointer>::getAs<capnp::DynamicStruct>(capnp::StructSchema) Note that `BuilderFor_<...>::Type` here ends up being a typedef for `DynamicStruct::Builder`. It seems weird to me that the symbol name would not substitute this typedef. Clang, meanwhile, mangles the symbol as: _ZN5capnp6OrphanINS_10AnyPointerEE5getAsINS_13DynamicStructEEENS_11BuilderFor_IT_Xclgssr5capnpE4kindIS6_EEEE4TypeENS_12StructSchemaE Which `c++filt` does not seem to be able to demangle at all. But, it looks like `capnp::kind` is in there, suggesting that, again, the typedef wasn't substituted. I don't know who is right, but if we inline the whole thing, the problem goes away.
-
Kenton Varda authored
Fixes #251
-
Kenton Varda authored
Fixes #336
-
Kenton Varda authored
Fixes #363.
-
Kenton Varda authored
Fixes #403
-
Kenton Varda authored
Fixes #405
-
Kenton Varda authored
Fixes #435
-
Kenton Varda authored
Fixes #456
-
Kenton Varda authored
Configure Travis CI for Linux and OSX builds.
-
Kenton Varda authored
-
Kenton Varda authored
This is redundant since branches are usually open in order to become PRs, which get their own merged-with-master builds.
-
Kenton Varda authored
-
Kenton Varda authored
-