lz4/lib/dll/example/README.md

70 lines
2.9 KiB
Markdown
Raw Normal View History

LZ4 Windows binary package
2016-11-15 11:57:56 +00:00
====================================
2016-11-15 13:09:36 +00:00
#### The package contents
2016-11-15 11:57:56 +00:00
- `lz4.exe` : Command Line Utility, supporting gzip-like arguments
- `dll\liblz4.dll` : The DLL of LZ4 library
- `dll\liblz4.lib` : The import library of LZ4 library for Visual C++
- `example\` : The example of usage of LZ4 library
- `include\` : Header files required with LZ4 library
2016-11-15 11:57:56 +00:00
- `static\liblz4_static.lib` : The static LZ4 library
2016-11-16 09:53:06 +00:00
#### Usage of Command Line Interface
Command Line Interface (CLI) supports gzip-like arguments.
By default CLI takes an input file and compresses it to an output file:
```
Usage: lz4 [arg] [input] [output]
2016-11-16 09:53:06 +00:00
```
The full list of commands for CLI can be obtained with `-h` or `-H`. The ratio can
be improved with commands from `-3` to `-16` but higher levels also have slower
compression. CLI includes in-memory compression benchmark module with compression
levels starting from `-b` and ending with `-e` with iteration time of `-i` seconds.
CLI supports aggregation of parameters i.e. `-b1`, `-e18`, and `-i1` can be joined
into `-b1e18i1`.
2016-11-16 09:53:06 +00:00
2016-11-15 11:57:56 +00:00
#### The example of usage of static and dynamic LZ4 libraries with gcc/MinGW
2016-11-16 08:53:07 +00:00
Use `cd example` and `make` to build `fullbench-dll` and `fullbench-lib`.
2016-11-15 11:57:56 +00:00
`fullbench-dll` uses a dynamic LZ4 library from the `dll` directory.
`fullbench-lib` uses a static LZ4 library from the `lib` directory.
#### Using LZ4 DLL with gcc/MinGW
The header files from `include\` and the dynamic library `dll\liblz4.dll`
2016-11-15 11:57:56 +00:00
are required to compile a project using gcc/MinGW.
The dynamic library has to be added to linking options.
2016-11-15 11:57:56 +00:00
It means that if a project that uses LZ4 consists of a single `test-dll.c`
2016-11-22 10:14:11 +00:00
file it should be linked with `dll\liblz4.dll`. For example:
2016-11-15 11:57:56 +00:00
```
2016-11-16 08:53:07 +00:00
gcc $(CFLAGS) -Iinclude\ test-dll.c -o test-dll dll\liblz4.dll
2016-11-15 11:57:56 +00:00
```
The compiled executable will require LZ4 DLL which is available at `dll\liblz4.dll`.
#### The example of usage of static and dynamic LZ4 libraries with Visual C++
2016-11-16 08:53:07 +00:00
Open `example\fullbench-dll.sln` to compile `fullbench-dll` that uses a
2016-11-15 12:49:20 +00:00
dynamic LZ4 library from the `dll` directory. The solution works with Visual C++
2010 or newer. When one will open the solution with Visual C++ newer than 2010
then the solution will upgraded to the current version.
2016-11-15 11:57:56 +00:00
#### Using LZ4 DLL with Visual C++
The header files from `include\` and the import library `dll\liblz4.lib`
are required to compile a project using Visual C++.
2016-11-15 12:49:20 +00:00
1. The header files should be added to `Additional Include Directories` that can
be found in project properties `C/C++` then `General`.
2016-11-15 11:57:56 +00:00
2. The import library has to be added to `Additional Dependencies` that can
be found in project properties `Linker` then `Input`.
If one will provide only the name `liblz4.lib` without a full path to the library
the directory has to be added to `Linker\General\Additional Library Directories`.
2016-11-15 12:49:20 +00:00
2016-11-15 11:57:56 +00:00
The compiled executable will require LZ4 DLL which is available at `dll\liblz4.dll`.