-
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 |
---|---|---|
c++ | Loading commit data... | |
doc | Loading commit data... | |
highlighting | Loading commit data... | |
security-advisories | Loading commit data... | |
.gitignore | Loading commit data... | |
.travis.yml | Loading commit data... | |
CONTRIBUTORS | Loading commit data... | |
LICENSE | Loading commit data... | |
README.md | Loading commit data... | |
RELEASE-PROCESS.md | Loading commit data... | |
appveyor.yml | Loading commit data... | |
mega-test-kenton-home.cfg | Loading commit data... | |
mega-test-kenton-work.cfg | Loading commit data... | |
mega-test-quick.cfg | Loading commit data... | |
mega-test.py | Loading commit data... | |
release.sh | Loading commit data... | |
style-guide.md | Loading commit data... | |
super-test.sh | Loading commit data... |