e28c5cd7ac
--enable-static-cryptsetup adds binaries suffixed with .static, e.g. cryptsetup.static, and those binaries have extra flags set to enable them to be built statically. It doesn't change how the main binaries are built — they're compiled correctly because pkgsStatic sets up all the necessary compiler flag anyway. So as far as I can tell, all --enable-static-cryptsetup gets us is duplicate binaries that take up disk space unnecessarily. |
||
|---|---|---|
| .. | ||
| bsd | ||
| darwin | ||
| linux | ||
| solo5 | ||
| windows | ||