wimlib

Yeah, the use of 'struct timespec' in the API was probably a mistake. The solution will be to define a compatible structure in wimlib.h for Visual Studio to use. I don't have a Visual Studio setup right now but you can try my proposed fix at https://wimlib.net/git/?p=wimlib;a=blob_plain;f=include/wi...

I went ahead and added directions to README.WINDOWS for running tools/make-windows-release, similar to what you suggested. I did make it say to clone the git repository, which avoids the missing files. For now I think it's reasonable for tools/ to be in the git repository only. Thanks for the sugges...

Great! I wasn't expecting tools/make-windows-release to work on Windows, but it looks like you got it working in Cygwin without too much trouble. The absence of build-aux/nasm_lt.sh from the release tarball is a bug. I'll add it in the next version. The absence of the tools directory is intentional,...

I assume you're talking about creating a libwim DLL with its third-party dependencies linked into it, as opposed to creating a libwim static library. I prepare the official Windows releases on Linux using the script tools/make-windows-release. As part of the process, libxml2 and winpthreads get down...

Apparently you hit a file size limit on the filesystem where you were creating the WIM archive. This is not a limitation with wimlib or with the WIM file format; you'd almost certainly get this same error with any application that attempts to create a large file on the same filesystem.

It's not possible to specify a custom WimBootCompress.ini for apply per se, but any existing WimBootCompress.ini in the image will be honored, and it's possible to add one beforehand by updating the image (or by exporting a copy of the image and updating the copy).

No, currently there isn't a way to do this through progress functions. Also, as currently designed, wimlib doesn't really do "per file" extraction progress, but rather provides statistics for calculating a percentage complete. wimlib is more focused on extracting the files --- or the whole...

It's actually the same NTFS-3G bug, more or less. The earlier fix was incomplete.

I've written what I believe to be a correct fix and sent it to the NTFS-3G mailing list.

I've also attached the proposed patch to this post, so you can try it if you're interested.

No, there aren't (yet) any options that control the printed output of wimlib-imagex.

Yes, it is indeed the bug which was discussed on the NTFS-3G forum thread I referenced above. It was fixed by an NTFS-3G patch only six weeks ago, so the fix is not yet present in a stable NTFS-3G release. If you are interested, you can find the latest NTFS-3G code at repository git://git.code.sf.ne...