| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Add $(LZ4DIR)/lz4frame.c to the list of prerequisites as the rule uses
that file.
Fixes: b192c86b ("[amalgamation] lz4frame.c")
|
|
|
|
|
|
| |
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
|
| |
| |
| |
| |
| |
| |
| | |
better handling of special conditions,
better scoping of variables.
Also : updated man page
|
|\ \
| |/
|/| |
Jpm makefile - as described in https://github.com/lz4/lz4/issues/688
|
| | |
|
| |
| |
| |
| | |
"install" in one place to try to isolate it.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
ensure this case is continuously tested on travis.
Update documentation on implicit output,
invite to not rely on implicit output in scripts.
|
| |
| |
| |
| |
| |
| | |
for potential redirection, if need be.
note : should probably converge all comparison operations onto CMP
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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`.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
and created target cxx17build
|
| | |
|
| |
| |
| |
| |
| | |
the program exit(),
so there is no need to track and dealloc every buffer.
|
| | |
|
| | |
|
|/ |
|
|\ |
|
| |
| |
| |
| |
| | |
which is unable to understand that the variable is necessarily initialized
in spite of an assert just before.
|
|/
|
|
|
|
| |
context is no longer dirty after a failed compressed block.
Actually, all indexes are fine.
It remains compatible with continued streaming, and reset*_fast().
|
| |
|
|
|
|
| |
was a false positive, but better remove it anyway
|
|
|
|
| |
ensure canary remains within buffer limits
|
|
|
|
|
|
| |
One test could write a canary value out of bound
in exceptional conditions involving multiple flushes
triggered by -s3421 -t462948.
|
| |
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
by making a full initialization
instead of a fast reset.
|
|
|
|
|
| |
it is now a pure initializer, for statically allocated states.
It can initialize any memory area, and because of this, requires size.
|
|
|
|
| |
not liked by mingw
|
| |
|
| |
|
|
|
|
|
| |
level down 5->4
size down 6G->5G
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- promoted LZ4_resetStream_fast() to stable
- moved LZ4_resetStream() into deprecate, but without triggering a compiler warning
- update all sources to no longer rely on LZ4_resetStream()
note : LZ4_initStream() proposal is slightly different :
it's able to initialize any buffer, provided that it's large enough.
To this end, it accepts a void*, and returns an LZ4_stream_t*.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
- promoted LZ4_resetStreamHC_fast() to stable
- moved LZ4_resetStreamHC() to deprecated (but do not generate a warning yet)
- Updated doc, to highlight difference between init and reset
- switched all invocations of LZ4_resetStreamHC() onto LZ4_initStreamHC()
- misc: ensure `make all` also builds /tests
|
|
|
|
| |
updated modification
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
add a test to check long sequences (#631)
|