I think that the goal here is to have Deken packages self “operational”, not needing Dlls outside its folder.
Here's a list of all Dlls that were used by Extended 0.44: (1)
Since all of these have to be included in the appropriate Deken pkg, I think its not necessary to recompile externals.
I understand what you mean by using vanilla`s VS, but there would be lots of cases where the Dlls have to be included because there are no substitutes in the target computer.
The good news is that the Dlls can be placed in the same folder as the externals (I did a couple of tests, have to make more)
(1):
libdca-0.dll
libdl.dll
libfftw3-3.dll
libfftw3f-3.dll
libfreetype-6.dll
libgavl-1.dll
libgcc_s_dw2-1.dll
libgnurx-0.dll
libjack.dll
libjpeg.dll
libmp3lame-0.dll
libogg-0.dll
libopenjpeg-2.dll
libpng-3.dll
libpng12-0.dll
libsndfile-1.dll
libstdc++-6.dll
libtheora-0.dll
libtheoradec-1.dll
libtheoraenc-1.dll
libtiff-3.dll
libtiffxx-3.dll
libvorbis-0.dll
libvorbisenc-2.dll
libvorbisfile-3.dll
libx264-116.dll
libz-1.dll
msvcr71.dll
pthreadGC2.dll
Mensaje telepatico asistido por maquinas.
From: chakekatzil@gmail.com
Date: Mon, 11 Jul 2016 13:49:37 -0400
Subject: Re: [PD] w32 Deken package issues.
To: lucarda27@hotmail.com
CC: pd-list@lists.iem.at