Lines Matching +full:fullbench +full:- +full:dll

6 - `lz4.exe`                  : Command Line Utility, supporting gzip-like arguments
7 - `dll\liblz4.dll`           : The DLL of LZ4 library
8 - `dll\liblz4.lib`           : The import library of LZ4 library for Visual C++
9 - `example\`                 : The example of usage of LZ4 library
10 - `include\`                 : Header files required with LZ4 library
11 - `static\liblz4_static.lib` : The static LZ4 library
16 Command Line Interface (CLI) supports gzip-like arguments.
21 The full list of commands for CLI can be obtained with `-h` or `-H`. The ratio can
22 be improved with commands from `-3` to `-16` but higher levels also have slower
23 compression. CLI includes in-memory compression benchmark module with compression
24 levels starting from `-b` and ending with `-e` with iteration time of `-i` seconds.
25 CLI supports aggregation of parameters i.e. `-b1`, `-e18`, and `-i1` can be joined
26 into `-b1e18i1`.
31 Use `cd example` and `make` to build `fullbench-dll` and `fullbench-lib`.
32 `fullbench-dll` uses a dynamic LZ4 library from the `dll` directory.
33 `fullbench-lib` uses a static LZ4 library from the `lib` directory.
36 #### Using LZ4 DLL with gcc/MinGW
38 The header files from `include\` and the dynamic library `dll\liblz4.dll`
41 It means that if a project that uses LZ4 consists of a single `test-dll.c`
42 file it should be linked with `dll\liblz4.dll`. For example:
44     gcc $(CFLAGS) -Iinclude\ test-dll.c -o test-dll dll\liblz4.dll
46 The compiled executable will require LZ4 DLL which is available at `dll\liblz4.dll`.
51 Open `example\fullbench-dll.sln` to compile `fullbench-dll` that uses a
52 dynamic LZ4 library from the `dll` directory. The solution works with Visual C++
57 #### Using LZ4 DLL with Visual C++
59 The header files from `include\` and the import library `dll\liblz4.lib`
69 The compiled executable will require LZ4 DLL which is available at `dll\liblz4.dll`.