aboutsummaryrefslogtreecommitdiff
path: root/src/liblzma/lzma/lzma2_encoder.c (follow)
AgeCommit message (Collapse)AuthorFilesLines
2009-11-15Fix wrong indentation caused by incorrect settingsLasse Collin1-3/+3
in the text editor.
2009-11-14Fix a design error in liblzma API.Lasse Collin1-25/+34
Originally the idea was that using LZMA_FULL_FLUSH with Stream encoder would read the filter chain from the same array that was used to intialize the Stream encoder. Since most apps wouldn't use LZMA_FULL_FLUSH, most apps wouldn't need to keep the filter chain available after initializing the Stream encoder. However, due to my mistake, it actually required keeping the array always available. Since setting the new filter chain via the array used at initialization time is not a nice way to do it for a couple of reasons, this commit ditches it and introduces lzma_filters_update(). This new function replaces also the "persistent" flag used by LZMA2 (and to-be-designed Subblock filter), which was also an ugly thing to do. Thanks to Alexey Tourbin for reminding me about the problem that Stream encoder used to require keeping the filter chain allocated.
2009-04-13Put the interesting parts of XZ Utils into the public domain.Lasse Collin1-12/+5
Some minor documentation cleanups were made at the same time.
2009-01-27Added initial support for preset dictionary for raw LZMA1Lasse Collin1-5/+7
and LZMA2. It is not supported by the .xz format or the xz command line tool yet.
2009-01-19Move some LZMA2 constants to lzma2_encoder.h so that theyLasse Collin1-13/+0
can be used outside lzma2_encoder.c.
2008-12-15Bunch of liblzma API cleanups and fixes.Lasse Collin1-3/+3
2008-12-09Make the memusage functions of LZMA1 and LZMA2 encodersLasse Collin1-1/+4
to validate the filter options. Add missing validation to LZMA2 encoder when options are changed in the middle of encoding.
2008-09-27Some API changes, bug fixes, cleanups etc.Lasse Collin1-17/+10
2008-08-28Sort of garbage collection commit. :-| Many things are stillLasse Collin1-0/+406
broken. API has changed a lot and it will still change a little more here and there. The command line tool doesn't have all the required changes to reflect the API changes, so it's easy to get "internal error" or trigger assertions.