Skip to content

Commit b9b804d

Browse files
committed
Update README to reflect new build option
1 parent e2dafb9 commit b9b804d

File tree

1 file changed

+2
-7
lines changed

1 file changed

+2
-7
lines changed

README.md

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ on GitHub should compile and function properly and should be usable for making p
1616

1717
### Building
1818

19-
AshleyCPP uses the CMake build system and comes with three build targets; debug, release and test.
19+
AshleyCPP uses the CMake build system and comes with three build targets; the debug library, "AshleyCPP-d", the release library "AshleyCPP" and the imaginatively named executable "AshleyCPPTest". The test program has a hard dependency on Google Test.
2020

2121
To build the library from source, install a relatively recent version of CMake, navigate to a copy of the source and
2222
do the following:
@@ -25,12 +25,7 @@ do the following:
2525
cd build
2626
cmake ..
2727

28-
and then proceed to build in your preferred environment. For example using makefiles on Unix:
29-
30-
cmake ..
31-
make # builds the release (libAshleyCPP) and debug (libAshleyCPP-d) libraries
32-
make AshleyCPPTest # for building the test suite executable, requires gtest and pthreads
33-
28+
and proceed as normal for your environment. If you don't care about the tests, you can run `cmake -DEXCLUDE_TESTS=TRUE ..` and the dependency on GTest will be removed, just giving you the libraries.
3429

3530
### Usage Notes and API Changes
3631
While AshleyCPP strives to match the exported public API of the Java original, differences in the languages mean that

0 commit comments

Comments
 (0)