[PD] w32 Deken package issues.

[IOhannes m zmoelnig]

On 2016-07-13 10:12, Lucas Cordiviola wrote:
> On 2016-07-12 09:41, IOhannes m zmoelnig wrote:
>> yes. that's the microsoft way to ship dependencies.
> 
> Lets keep Microsoft out of this, this is a Pd and Pd externals issue.

no.
we can leave out my rant, but shipping dependencies multiple times *is*
the w32 way, and i do think we should follow that path.
the alternative - installing 3rd party dependencies to %pd%\bin or even
to %System% - is a very good way to break your system.

> How we update all w32 Deken pkgs?

this probably sounds a bit obvious:
we identify the broken packages, then identify the missing dlls for each.
then we repack the packages with the libraries included, and upload them)

i can do the second part (repackaging, re-uploading), if someone wades
through the first part (identification of missing parts) and provides
the result in a computer-readable form.
(there are probably ways to automate the first part using
DependencyWalker of similar, but i don't know them)


fgmasdr
IOhannes

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20160713/33fb0aeb/attachment.sig>