From 9e147ba41ec632a620191479afd9bd8ffb5e79e0 Mon Sep 17 00:00:00 2001 From: Bob Polis Date: Tue, 24 Dec 2024 10:40:34 +0100 Subject: [PATCH] Add `make test` explanation --- README.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 1be85c8..ddcee39 100644 --- a/README.md +++ b/README.md @@ -35,13 +35,14 @@ the Makefile). The `premake.make` typically defines some Make variables, whereas the `postmake.make` typically contains extra Make targets. -The `premake.make` is mandatory, because it defines the **name** of the tool or -library, and its **version**. This is also where you declare external +The `premake.make` is mandatory, because it defines the *name* of the tool or +library, and its *version*. This is also where you declare external dependencies. -Available Make targets are: +Available Make targets for your project are: - `make` will build the tool or library; +- `make test` will build and run tests, using the Boost Unit Test Framework; - `sudo make install` will install it, and all of its accompanying files; - `make clean` will remove compiled object files, but will keep a previously built tool or library, and the precompiled header;