From fb8ec13127fda33b7e12a33844df93fb24ca1131 Mon Sep 17 00:00:00 2001 From: LoRd_MuldeR Date: Sat, 3 Dec 2022 16:07:38 +0100 Subject: [PATCH] Updated README file. --- README.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/README.md b/README.md index f0b6dbe..3a48226 100644 --- a/README.md +++ b/README.md @@ -869,6 +869,26 @@ LibHashSet is ***thread-safe***, in the sense that all public functions operate However, LibHashSet does **nothing** to synchronize access to a particular `hash_set_t` or `hash_map_t` instance! Consequently, in situations where the *same* instance needs to be shared across *multiple* concurrent threads, the calling application is responsible for serializing all access to the "shared" instance, e.g. by using a [*mutex*](https://pubs.opengroup.org/onlinepubs/007908799/xsh/pthread_mutex_lock.html) lock! +Build Instructions +================== + +This section describes how to build LibHashSet from the source codes. + +Windows +------- + +On Microsoft Windows, project/solution files are provided to build LibHashSet with [Microsoft Visual Studio](https://visualstudio.microsoft.com/). + +LibHashSet also can be built using *GCC* or *Clang* via [MSYS2/Mingw-w64](https://www.msys2.org/) or [Cygwin](https://www.cygwin.com/). Be sure that *GCC* (or *Clang*) and *GNU make* are installed. Then run `make` from the project base directory, in the MSYS2 (or Cygwin) shell! + +Linux and *BSD +------------------ + +On Linux or *BSD, building LibHashSet with *GCC* or *Clang* is recommended. Also *GNU make* is required to build. + +Simply run `make` (or `gmake`, if on *BSD) from the project base directory. That's it! + + License =======