On Tue, Feb 6, 2018 at 10:43 AM, IOhannes m zmoelnig <zmoelnig@iem.at> wrote:

in Pd-extended, there are 10 out of 112 (different) libraries usable on
Windows in the entire deken repositories that have the libpthread
library included, presumably because they actually need this library.

of these 10 libraries, the following 6 come from the big Pd-extended
import, and have not been updated since (and are presumably unmaintained):
- hidin
- iemxmlrpc
- mrpeach (+ net)
- pdogg
- unauthorized

I have been workjng on mrpeach in sourceforge svn recently, so I _am_ maintaining it, although pthreads was probably imported from somewhere else. AFAIK it's only needed for some of the net objects like [tcpserver].

I am really not sure how to build an external on a Windows system. All the docs in pdinfo are several years old.

The readme here:
https://github.com/pure-data/pure-data/tree/master/msw

talks about some hybrid build system on wine using mingw and msw but gives no indication of how to set it up.

I don't see why one must use a linux box to compile for Windows, it's just offputting. On Windows, I usually give up trying after a day or so of filling my drive with mingw and cygwin and getting nowhere.

I also try to build using Visual Studio, but there again the versions are usually incompatible with whatever pd.lib was built with.
As I've mentioned before, the c runtime libraries that mingw and msw link against are not compatible, and possibly neither are the pthread dlls.

It would be nice if the 'official' tool chain for building externals that work with vanilla Pd on a Windows machine in 2018 could be explicitly documented somewhere.

Martin