v1.14.4
v1.14.3
v1.14.2
Improve encoding detection of wimupdate command files Make wimupdate command files (read from stdin) and wimcapture source list files be interpreted as UTF-8 or UTF-16LE (autodetected). Previously these files were interpreted as the Windows codepage or UTF-16LE on Windows (autodetected), and UTF-8 on non-Windows. This makes these files be consistent with wimextract pathlist files and wimcapture config files, which already had the behavior of "autodetect UTF-8 or UTF-16LE on all platforms". Resolves https://wimlib.net/forums/viewtopic.php?p=1545
Align stack when entering wimlib on 32-bit x86 This may resolve https://wimlib.net/forums/viewtopic.php?t=669. The reported crash happened in sha1_blocks_x86_avx_bmi2() on the first instruction that writes to the stack with vmovqda. That suggests the stack was misaligned. If this indeed fixes the bug, then it has actually always existed but it got exposed by new code in v1.14.0.
v1.14.1
v1.14.0
wimlib.h: remove outdated list of Windows architectures
Convert README* and NEWS to Markdown This is the usual convention for new projects.
Fix clang warnings about inconsistent use of dllexport In MSYS2, clang emits many warnings like the following: warning: redeclaration of 'wimlib_add_empty_image' should not add 'dllexport' attribute The problem is that dllexport is used when defining the wimlib API functions but not when declaring them. Fix this by using dllexport in both places.
v1.13.6
wimlib.h: remove duplicate 'the'
Remove some unnecessary configure options Remove support for the following options which aren't really useful and probably aren't being used by anyone: * --disable-assertions * --disable-error-messages * --disable-multithreaded-compression
wimlib_iterate_dir_tree(): don't checksum unhashed blobs wimlib_iterate_dir_tree() on a modified-but-not-committed image is very slow because it checksums all unhashed blobs. This was originally implemented by commit 681faad85f73 ("wimlib_iterate_dir_tree(): checksum unhashed blobs"), presumably to make the sha1_hash field always valid. However, I can't remember a real use case for this. The current behavior is causing problems, so let's just revert it and update the documentation accordingly. Reported at https://wimlib.net/forums/viewtopic.php?f=1&t=572
v1.13.5
v1.13.4
Add support for a data recovery mode Add support for extracting file data even if it is corrupted (i.e. if its hash doesn't match or some of its chunks can't be decompressed). This isn't recommended for general use, but it could be useful for recovering data from a corrupted WIM archive.
Fix slow progress updating for wimsplit wimsplit only prints a progress message when starting each WIM part. That could be very infrequently since each part could be gigabytes. Fix it to update the progress regularly as data is written, like the other wimlib-imagex commands do. This required changing the library to report WIMLIB_PROGRESS_MSG_WRITE_STREAMS messages from wimlib_split() and include the completed compressed size in them. Reported at https://www.reddit.com/r/pcmasterrace/comments/hagu4k/wimlibimagex_split_stuck_at_0
v1.13.3
v1.13.2