Files
wuffs/release/c
Nigel Tao 555e8eaaa3 Add gif.config_decoder (part 2 of 2)
This runs script/preprocess-wuffs.go as foreshadowed by the previous
commit 1aa50163 "Add gif.config_decoder (part 1 of 2)".

The new gif.config_decoder type is largely a copy/paste (with minor
edits) of the existing decoder type, but it can decode GIF animation
metadata (e.g. frame timings) without the memory requirements of a
complete GIF decoder (which can also decode pixels). As of this commit,
sizeof(config_decoder) and sizeof(decoder) is 1320 and 65024, a
difference of over 62 KiB.

The trade-off is that binary size increased by around 1.5x or 18K for
the GIF package. Future refactorings might be able to claw that back,
but it might not.

"wuffs genlib; ls -l gen/lib/c/*/*gif* | awk etc" output:

Before:
25904 gen/lib/c/clang-5.0-dynamic/wuffs-std-gif.lo
26424 gen/lib/c/clang-5.0-static/wuffs-std-gif.o
30480 gen/lib/c/gcc-dynamic/wuffs-std-gif.lo
30064 gen/lib/c/gcc-static/wuffs-std-gif.o

After:
41168 gen/lib/c/clang-5.0-dynamic/wuffs-std-gif.lo
42328 gen/lib/c/clang-5.0-static/wuffs-std-gif.o
49040 gen/lib/c/gcc-dynamic/wuffs-std-gif.lo
48304 gen/lib/c/gcc-static/wuffs-std-gif.o
2020-02-05 17:25:39 +11:00
..
2019-12-20 00:47:36 +11:00
2019-12-20 00:52:23 +11:00

Releases (in the C Programming Language)

Wuffs the Library ships as a "single file C library", also known as a "header file library".

To use that library in your C/C++ project, you just need to copy one file from this directory, or otherwise integrate that one file into your build system. Typically, pick the latest stable version (but not the unsupported snapshot), with a filename like wuffs-vMAJOR.MINOR.c for version MAJOR.MINOR.

To use that single file as a "foo.c"-like implementation, instead of a "foo.h"-like header, #define WUFFS_IMPLEMENTATION before #include'ing or compiling it.

Latest Stable Version

Version 0.2 (December 2019) is the latest stable version. Stable means that its API won't change any further, but being a "version 0.x" means that:

  • It will not have long term support.
  • Newer versions make no promises about compatibility.