search

libvips / build-win64-mxe

76 stars 15 forks source link

Please provide an artifact with the debug symbols for libvips for each released version #36

Closed JCMais closed 2 years ago

JCMais commented 2 years ago

This will make it easier to debug libvips and packages that may depend on it.

kleisauke commented 2 years ago

I'm a bit reluctant to distribute debug versions of these Windows binaries because of performance reasons. There are also legal reasons that make this unlikely to happen, since commit https://github.com/libvips/build-win64-mxe/commit/06090f02a66256076298739d8b475b8756f19e48 binaries built with --with-debug would link against ucrtbased.dll. This DLL is not redistributable, so it's not possible to distribute applications built with it (see also https://github.com/mstorsjo/llvm-mingw/issues/228).

You're always free to build these binaries by yourself. The debug versions of the pre-built Windows binaries distributed by sharp can be built with:

./build.sh web x86_64 static --with-debug
./build.sh web i686 static --with-debug
./build.sh web aarch64 static --with-debug

Note that the first time build will take a long time, because LLVM and Rust have to be built from source. Moreover, the produced zipballs are huge (~100mb).

JCMais commented 2 years ago

Hi @kleisauke. No problem, all the points you mentioned make sense. I will try building the debug version myself and see how that goes.