- 03 May, 2016 1 commit
-
-
Branislav Katreniak authored
It is useful for autoconf based installations.
-
- 11 Apr, 2016 1 commit
-
-
Alex Richardson authored
This makes it a lot easier for CMake based projects to use Cap'n Proto. Example usage: find_package(CapnProto) capnp_generate_cpp(FOO_SRCS FOO_HDRS foo.capnp) add_executable(foo main.cpp ${FOO_SRCS}) target_link_libraries(foo CapnProto::capnp CapnProto::capnp-rpc) This is a lot better than the previous variable based solution since linking to nonexistent targets is an error whereas an empty variable expansion (e.g. due to typos) will be silently ignored. It also makes sure that the right compiler flags, include directories, defines and link libraries are passed to the compiler for that target without needing any other include_directories(), etc.
-
- 29 Mar, 2016 1 commit
-
-
Branislav Katreniak authored
-
- 26 Jan, 2016 1 commit
-
-
Thomas Sanchez authored
-
- 12 Dec, 2014 2 commits
-
-
Kenton Varda authored
The idea behind the directory organization was that we might have official implementations for other languages in other top-level directories, as siblings to the c++ directory. It seems implausible that we'd use CMake as a meta-build-system over all of these. Another reason for this change is that the release tarball actually contains only the c++ subdirectory. We probably want to include cmake files in the release.
-
Kenton Varda authored
-
- 29 Oct, 2014 2 commits
-
-
Philip Quinn authored
-
Philip Quinn authored
Also, use pkg-config (if available) to get hints about the paths.
-
- 28 Oct, 2014 1 commit
-
-
Philip Quinn authored
-
- 20 Oct, 2014 1 commit
-
-
Philip Quinn authored
-