lz4/lib
2016-11-12 15:50:29 -08:00
..
.gitignore lz4 version source from lz4.h 2016-09-02 22:04:16 -07:00
liblz4.def DLL exports only functions defined in liblz4.def 2016-11-09 16:07:28 +01:00
liblz4.pc.in lz4 version source from lz4.h 2016-09-02 22:04:16 -07:00
LICENSE Makefile : generates *.o for faster processing 2015-08-15 17:21:45 +01:00
lz4.c fixed __GNUC__ macro 2016-11-12 13:30:02 -08:00
lz4.h fixed __GNUC__ macro 2016-11-12 13:30:02 -08:00
lz4frame_static.h updated frametest 2016-11-11 15:11:56 -08:00
lz4frame.c enabled deprecation warnings on remaining obsolete functions 2016-11-12 08:48:42 -08:00
lz4frame.h updated frametest 2016-11-11 15:11:56 -08:00
lz4hc.c made lz4hc explicitly dependent on lz4 2016-11-12 15:50:29 -08:00
lz4hc.h made lz4hc explicitly dependent on lz4 2016-11-12 15:50:29 -08:00
Makefile fixed make install 2016-11-09 16:23:08 +01:00
README.md Fix license and remove references to zstd 2016-11-10 17:27:56 -08:00
xxhash.c updated xxhash lib 2016-11-10 18:34:49 -08:00
xxhash.h updated xxhash lib 2016-11-10 18:34:49 -08:00

LZ4 - Library Files

The directory contains many files, but depending on project's objectives, not all of them are necessary.

Minimal LZ4 build

The minimum required is lz4.c and lz4.h, which will provide the fast compression and decompression algorithm.

The High Compression variant of LZ4

For more compression at the cost of compression speed, the High Compression variant lz4hc is available. It's necessary to add lz4hc.c and lz4hc.h. The variant still depends on regular lz4 source files. In particular, the decompression is still provided by lz4.c.

Compatibility issues

In order to produce files or streams compatible with lz4 command line utility, 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. In order to work properly, lz4frame needs lz4 and lz4hc, and also xxhash, which provides error detection. (Advanced stuff : It's possible to hide xxhash symbols into a local namespace. This is what liblz4 does, to avoid symbol duplication in case a user program would link to several libraries containing xxhash symbols.)

Advanced API

A more complex lz4frame_static.h is also provided. It contains definitions which are not guaranteed to remain stable within future versions. It must be used with static linking only.

Using MinGW+MSYS to create DLL

DLL can be created using MinGW+MSYS with the "make liblz4" command. This command creates "liblz4.dll" and the import library "liblz4.dll.a". To compile a project the import 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.dll.a". For example:

    gcc $CFLAGS test-dll.c -o test-dll liblz4.dll.a

Miscellaneous

Other files present in the directory are not source code. There are :

  • LICENSE : contains the BSD license text
  • Makefile : script to compile or install lz4 library (static or dynamic)
  • liblz4.pc.in : for pkg-config (make install)
  • README.md : this file

License

All source material within lib directory are BSD 2-Clause licensed. See LICENSE for details. The license is also repeated at the top of each source file.