-
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.
f21d3819
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.
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
cmake | Loading commit data... | |
ekam-provider | Loading commit data... | |
m4 | Loading commit data... | |
samples | Loading commit data... | |
src | Loading commit data... | |
CMakeLists.txt | Loading commit data... | |
LICENSE.txt | Loading commit data... | |
Makefile.am | Loading commit data... | |
Makefile.ekam | Loading commit data... | |
README.txt | Loading commit data... | |
afl-fuzz.sh | Loading commit data... | |
capnp-json.pc.in | Loading commit data... | |
capnp-rpc.pc.in | Loading commit data... | |
capnp.pc.in | Loading commit data... | |
configure.ac | Loading commit data... | |
kj-async.pc.in | Loading commit data... | |
kj.pc.in | Loading commit data... | |
regenerate-bootstraps.sh | Loading commit data... | |
setup-autotools.sh | Loading commit data... | |
setup-ekam.sh | Loading commit data... |