summaryrefslogtreecommitdiffstats
path: root/lib
diff options
context:
space:
mode:
authorPrzemyslaw Skibinski <inikep@gmail.com>2016-11-16 07:59:18 (GMT)
committerPrzemyslaw Skibinski <inikep@gmail.com>2016-11-16 07:59:18 (GMT)
commit2e10aab20f17adfffb2379e828124be12c774779 (patch)
tree3a0ea44e93d92ba5523b0d5d23ef392cd236859b /lib
parent4235e5e25f79828e6192eb17fac7a24992aed07d (diff)
downloadlz4-2e10aab20f17adfffb2379e828124be12c774779.zip
lz4-2e10aab20f17adfffb2379e828124be12c774779.tar.gz
lz4-2e10aab20f17adfffb2379e828124be12c774779.tar.bz2
MinGW doesn't require the import library at all
Diffstat (limited to 'lib')
-rw-r--r--lib/README.md8
-rw-r--r--lib/dll/README.md12
-rw-r--r--lib/dll/fullbench-dll/Makefile2
3 files changed, 13 insertions, 9 deletions
diff --git a/lib/README.md b/lib/README.md
index 430be1f..18793d4 100644
--- a/lib/README.md
+++ b/lib/README.md
@@ -42,12 +42,16 @@ It must be used with static linking ***only***.
DLL can be created using MinGW+MSYS with the `make liblz4` command.
This command creates `dll\liblz4.dll` and the import library `dll\liblz4.lib`.
-To compile a project the import library has to be added to linking options.
+The import library is only required with Visual C++.
+The header files `lz4.h`, `lz4hc.h`, `lz4frame.h` and the dynamic library
+`dll\liblz4.dll` are required to compile a project using gcc/MinGW.
+The dynamic library has to be added to linking options.
It means that if a project that uses LZ4 consists of a single `test-dll.c`
file it should be compiled with "liblz4.lib". For example:
```
- gcc $(CFLAGS) test-dll.c -o test-dll liblz4.lib
+ gcc $(CFLAGS) -Iinclude/ test-dll.c -o test-dll dll\liblz4.dll
```
+The compiled executable will require LZ4 DLL which is available at `dll\liblz4.dll`.
#### Miscellaneous
diff --git a/lib/dll/README.md b/lib/dll/README.md
index 779b8ae..bb3dbd6 100644
--- a/lib/dll/README.md
+++ b/lib/dll/README.md
@@ -4,9 +4,9 @@ The static and dynamic LZ4 libraries
#### The package contents
- `dll\liblz4.dll` : The DLL of LZ4 library
-- `dll\liblz4.lib` : The import library of LZ4 library
-- `include\` : Header files required with LZ4 library
+- `dll\liblz4.lib` : The import library of LZ4 library for Visual C++
- `fullbench\` : The example of usage of LZ4 library
+- `include\` : Header files required with LZ4 library
- `static\liblz4_static.lib` : The static LZ4 library
@@ -19,13 +19,13 @@ Use `make` to build `fullbench-dll` and `fullbench-lib`.
#### Using LZ4 DLL with gcc/MinGW
-The header files from `include\` and the import library `dll\liblz4.lib`
+The header files from `include\` and the dynamic library `dll\liblz4.dll`
are required to compile a project using gcc/MinGW.
-The import library has to be added to linking options.
+The dynamic library has to be added to linking options.
It means that if a project that uses LZ4 consists of a single `test-dll.c`
-file it should be compiled with "liblz4.lib". For example:
+file it should be compiled with "liblz4.dll". For example:
```
- gcc $(CFLAGS) -Iinclude/ test-dll.c -o test-dll dll\liblz4.lib
+ gcc $(CFLAGS) -Iinclude/ test-dll.c -o test-dll dll\liblz4.dll
```
The compiled executable will require LZ4 DLL which is available at `dll\liblz4.dll`.
diff --git a/lib/dll/fullbench-dll/Makefile b/lib/dll/fullbench-dll/Makefile
index 32e13fc..680e1b6 100644
--- a/lib/dll/fullbench-dll/Makefile
+++ b/lib/dll/fullbench-dll/Makefile
@@ -54,7 +54,7 @@ fullbench-lib: fullbench/fullbench.c fullbench/xxhash.c
$(CC) $(FLAGS) $^ -o $@$(EXT) static/liblz4_static.lib
fullbench-dll: fullbench/fullbench.c fullbench/xxhash.c
- $(CC) $(FLAGS) $^ -o $@$(EXT) -DLZ4_DLL_IMPORT=1 dll/liblz4.lib
+ $(CC) $(FLAGS) $^ -o $@$(EXT) -DLZ4_DLL_IMPORT=1 dll/liblz4.dll
clean:
@$(RM) fullbench-dll$(EXT) fullbench-lib$(EXT) \