lz4/lib/README.md

80 lines
3.1 KiB
Markdown
Raw Normal View History

LZ4 - Library Files
================================
The `/lib` directory contains many files, but depending on project's objectives,
2016-11-02 02:14:04 +00:00
not all of them are necessary.
2016-11-10 16:49:42 +00:00
#### Minimal LZ4 build
2016-11-02 02:14:04 +00:00
The minimum required is **`lz4.c`** and **`lz4.h`**,
which provides the fast compression and decompression algorithm.
They generate and decode data using [LZ4 block format].
2016-11-10 16:49:42 +00:00
#### High Compression variant
2016-11-10 16:49:42 +00:00
For more compression ratio at the cost of compression speed,
the High Compression variant called **lz4hc** is available.
Add files **`lz4hc.c`** and **`lz4hc.h`**.
2018-09-13 23:14:00 +00:00
This variant also depends on regular `lib/lz4.*` source files.
2016-11-10 16:49:42 +00:00
2018-09-13 23:14:00 +00:00
#### Frame support, for interoperability
2016-11-10 16:49:42 +00:00
In order to produce compressed data compatible with `lz4` command line utility,
2016-11-02 02:14:04 +00:00
it's necessary to encode lz4-compressed blocks using the [official interoperable frame format].
This format is generated and decoded automatically by the **lz4frame** library.
Its public API is described in `lib/lz4frame.h`.
In order to work properly, lz4frame needs all other modules present in `/lib`,
including, lz4 and lz4hc, and also **xxhash**.
So it's necessary to include all `*.c` and `*.h` files present in `/lib`.
2016-11-10 16:49:42 +00:00
#### Advanced / Experimental API
2016-11-10 16:49:42 +00:00
2018-09-13 23:14:00 +00:00
Definitions which are not guaranteed to remain stable in future versions,
are protected behind macros, such as `LZ4_STATIC_LINKING_ONLY`.
As the name implies, these definitions can only be invoked
in the context of static linking ***only***.
Otherwise, dependent application may fail on API or ABI break in the future.
The associated symbols are also not present in dynamic library by default.
Should they be nonetheless needed, it's possible to force their publication
by using build macro `LZ4_PUBLISH_STATIC_FUNCTIONS`.
2016-11-02 02:14:04 +00:00
2016-11-10 16:49:42 +00:00
#### Windows : using MinGW+MSYS to create DLL
2016-11-10 17:30:59 +00:00
2016-11-11 07:57:46 +00:00
DLL can be created using MinGW+MSYS with the `make liblz4` command.
2016-11-15 10:06:16 +00:00
This command creates `dll\liblz4.dll` and the import library `dll\liblz4.lib`.
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.
2016-11-11 07:57:46 +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-10 17:30:59 +00:00
```
2018-09-13 23:14:00 +00:00
$(CC) $(CFLAGS) -Iinclude/ test-dll.c -o test-dll dll\liblz4.dll
2016-11-10 17:30:59 +00:00
```
The compiled executable will require LZ4 DLL which is available at `dll\liblz4.dll`.
2016-11-10 17:30:59 +00:00
#### Miscellaneous
2016-11-10 16:49:42 +00:00
2016-11-02 02:14:04 +00:00
Other files present in the directory are not source code. There are :
- `LICENSE` : contains the BSD license text
- `Makefile` : `make` script to compile and install lz4 library (static and dynamic)
- dlltool can be overrided by setting DLLTOOL variable (useful when cross-compiling on Linux for Windows)
- `liblz4.pc.in` : for `pkg-config` (used in `make install`)
- `README.md` : this file
2016-11-03 12:25:20 +00:00
[official interoperable frame format]: ../doc/lz4_Frame_format.md
[LZ4 block format]: ../doc/lz4_Block_format.md
2016-11-10 16:49:42 +00:00
#### License
2016-11-10 16:49:42 +00:00
All source material within __lib__ directory are BSD 2-Clause licensed.
See [LICENSE](LICENSE) for details.
The license is also reminded at the top of each source file.