I can't get to it to until later, but let's stay in sync on this. In the mean time, you could propose your builds to Miller until we can figure out the character issues.

I have a new job (ZKM) and a Windows 10 install, so my plan is fix the autootools build issues on Windows. I'm sure I'll need your knowledge as you have gotten the farthest with this so far.

On Jul 25, 2017, at 3:55 PM, Christof Ressi <christof.ressi@gmx.at> wrote:

Hi Dan,

I know, there is more urgent stuff going on right now, but in case I forget:

I tried to compile Pd from git with asio support. My system is msys2 on Windows 7. When compiling portaudio, gcc can't find the necessary ASIO headers (which are in asio/ASIOSDK2). I tried to add the directory via configure (--includedir, CFLAGS, CPPFLAGS, ...) without success.

copying the following header files from ASIOSDK2 to /portaudio/portaudio/include did the trick:

asio.h
asiodrivers.h
asiodrvr.h
asiosys.h
combase.h
ginclude.h
iasiodrv.h
pc/asiolist.h (yes, asiolist.h has to be in a folder 'pc')

also, ASIO seems to link dynamically to libstdc++-6.dll from msys64/mingw32/bin. for me, there was an interference with another version of libstdc++-6.dll somewhere in my system. I also had this problem with openFrameworks. I think it's good to either link statically or to copy libstdc++-6.dll into Pd's bin folder. The latter is my personal solution for now. For OF, I always put it into the export folder so it gets copied automatically everytime I compile a new app. I can remember that other people had this problem with OF so I can imagine it could also be a problem with Pd.

Christof

--------
Dan Wilcox
@danomatika
danomatika.com
robotcowboy.com