[19/51] celix git commit: CELIX-338: Updated Building instructions

[pn...@apache.org]

CELIX-338: Updated Building instructions


Project: http://git-wip-us.apache.org/repos/asf/celix/repo
Commit: http://git-wip-us.apache.org/repos/asf/celix/commit/3b82dc86
Tree: http://git-wip-us.apache.org/repos/asf/celix/tree/3b82dc86
Diff: http://git-wip-us.apache.org/repos/asf/celix/diff/3b82dc86

Branch: refs/heads/feature/CELIX-335_deploy_refactoring
Commit: 3b82dc866095fb4d49e02a8e09502836ac1f26a7
Parents: 52daddd
Author: Bjoern Petri <bp...@apache.org>
Authored: Mon Jan 11 09:59:32 2016 +0100
Committer: Bjoern Petri <bp...@apache.org>
Committed: Mon Jan 11 09:59:32 2016 +0100

----------------------------------------------------------------------
 BUILDING | 17 +++++++----------
 1 file changed, 7 insertions(+), 10 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/celix/blob/3b82dc86/BUILDING
----------------------------------------------------------------------
diff --git a/BUILDING b/BUILDING
index 1271930..819d42b 100644
--- a/BUILDING
+++ b/BUILDING
@@ -42,16 +42,13 @@ Quick Start
 Unit testing using CppUTest
 ---------------------------
 
-Apache Celix has two build options that enable a set of unit tests. These tests
-are based on CUnit a fork of CppUTest. CUnit can simply be installed and is normally
-found by the CMake scripts, but for CppUTest a fork needs to be build.
-
-The fork can be found on https://github.com/abroekhuis/cpputest/tree/backup. Simply cloning, building
-and updating the build configuration to point to the build files should be enough.
-
-Some background, CppUTest doesn't support output parameters, but Celix's API relies heavily
-on those. The fork adds support for this.
-
+Apache Celix has build options that enable a set of unit tests for each component. These tests
+are based on CppUTest, which needs to be installed separately.
+To run the tests
+  $ make test
+To get a HTML page with the test coverage
+  $ make coverage
+The coverage results are found in <build_dir>/coverage_results/index.html
 
 Background information
 ----------------------