| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
for readability.
Mostly around --list capability
|
|
|
|
|
| |
detected by scan-build and cppcheck
fix #786
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows us to get the file size even when the input file is passed
via stdin. This fixes `--content-size` not working in situations like
$ lz4 -v --content-size < /tmp/test > /tmp/test.lz4
Warning : cannot determine input content size
With this change, it works.
Also helps with #904.
|
|
|
|
|
|
|
|
| |
variant of lz4 linking to liblz4 dynamic library
requires the dynamic library to expose static-only symbols (experimental API)
Example for #888
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Support the -D command line option for running benchmarks. The
benchmark code was slightly restructured to factor out the calls
that need to be different for each benchmark scenario. Since there
are now 4 scenarios (all combinations of fast/HC and with/without
dictionary), the logic was getting somewhat convoluted otherwise.
This was done by extending the compressionParameters struct that
previously contained just a single function pointer. It now
contains 4 function pointers for init/reset/compress/cleanup,
with the related state. The functions get a pointer to the
structure as their first argument (inspired by C++), so that they
can access the state values in the struct.
|
|
|
|
| |
utime was deprecated in POSIX 2008.
|
| |
|
|
|
|
| |
to reduce risks that future bug reports in `dev` branch report `v1.9.1` as the failing version.
|
|
|
|
| |
instead of stderr
|
| |
|
|
|
|
|
|
|
|
|
| |
Improve formatting
Include static assert
Use UTIL_fseek to handle potential fseek limitation
Be explicit when refusing to read from stdin
Properly free dctx after use
Include valgrind tests
|
| |
|
|
|
|
|
|
| |
Moved a few other tests to Makefiles.inc. Other things might need to go there.
Made a test for symlink appropriateness. Windows can NOT handle them the same way Unix-like operating systems do (if at all). This is mostly the same as the Visual C projects.
embed version info into .dll and .exes that are redistributed.
|
|\
| |
| | |
--list
|
| |
| |
| |
| |
| | |
strange, because it previous implementation, it would `exit()`,
so it should not matter ...
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
better handling of special conditions,
better scoping of variables.
Also : updated man page
|
| |
| |
| |
| | |
re-structure code, have everything into a single section of lz4io.c
|
| | |
|
| | |
|
| |
| |
| |
| | |
assert if in om_list mode
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| |_|/
|/| | |
Jpm makefile - as described in https://github.com/lz4/lz4/issues/688
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
ensure this case is continuously tested on travis.
Update documentation on implicit output,
invite to not rely on implicit output in scripts.
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This behavior has been preserved for compatibility with existing ecosystem.
But it's problematic, as some environment start `lz4` without identifying stdout as console by default,
leading to a change of behavior for a same line of script.
A more sensible policy would be to default to stdout only when input is stdin.
Soft change for the time being : keep the behavior, just print a warning message.
User should prefer `-c` to explicitly select `stdout`.
Also : updated tests in Makefile to explicitly select `stdout` with `-c`.
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
|
|
|
| |
seems to work properly
|
|
|
|
| |
can compress multiple files into stdout
|
|
|
|
|
|
|
|
| |
This is the reverse of `-BD`, and the current default.
This command can be useful to reverse a previous `-BD` command.
It may in the future be more important
if `lz4` switches to generating dependent blocks by default.
|
|
|
|
| |
with --favor-decSpeed
|
|
|
|
| |
as this is a very frequent source of confusion for new users.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
make it possible to generate LZ4-compressed block
with a controlled maximum offset (necessarily <= 65535).
This could be useful for compatibility with decoders
using a very limited memory budget (<64 KB).
Answer #154
|