Purr Data 2.5.0 is now available:

https://github.com/jonwwilkes/purr-data/releases/tag/2.5.0

Please report bugs here:

https://git.purrdata.net/jwilkes/purr-data/issues

Changes:

• add pd-lua library
• fix up dialog styling for GUI presets
• expand help browser search index to include the external library docs
• add preferences for setting when and from which docs the search browser creates an index
• port disis_munger~ to Purr Data from pd-l2ork 1.0 (experimental)
• fix the build scripts by adding toplevel makefile with new targets
• fix uninstall icon on Windows
• add dashed box around comments when in edit mode to show the maximum space they will take up

@alfonso.santimone Oops, typo-- I meant purr-data/packages/win32_inno/Makefile

@jancsika Oh i see thanks. Where can i find any doc about architecture flags?

@jancsika used
OPT_CFLAGS += -mcpu=x86-64 -mtune=core2

and here is the log in .sh format (some errors about architecture not supported by fluidsynth and other stuff)purr-data-w64-build-log-02.sh

some errors about architecture not supported by fluidsynth

That's apparently because the "helper" makefile called Makefile.pdlibbuilder which I used to quickly get a library up and running has the following comment in it under TODO:

# - Windows 64 bit support

You'll probably run into other similar problems in the externals.

@jancsika Yeah so as i thought there are several externals not supporting Win64. How can i deal with this? I guess is something in the makefile?

@alfonso.santimone I doubt there are really that many which don't work under Win64. After all, all those same externals work fine on 64-bit Linux. So it's probably just junk in the makefiles.

If you want you can go into purr-data/externals/Makefile and just remove the problem library name from the big list assigned to LIB_TARGETS. Do this for each problem library until you get a successful compilation. (And keep track of the ones you've removed.)

@jancsika Thanks i'll try some more divide and conquer
But i see that fluid~.c calls fluidsynth.h ..i can't find it in the directory structure of the whole purr-data folder...
given this

fluid~.c:1:0: error: CPU you selected does not support x86-64 instruction set
#include <fluidsynth.h>

fluid~.c:1:0: error: CPU you selected does not support x86-64 instruction set

i guess something has to be done in the fluid~ sources or in fluidsynth.h regarding architecture stuff

Excluded fluid~ then sendon try. Now i go with the 3rd try with Gem excluded (i commented out line 150 in t purr-data/externals/Makefile

Ok i excluded fluidsynth and Gem stuff so i don't see errors about thos..i het some errors about directory structure and inno setup stuff (is inno setup for 32bit only maybe?) here is the .sh log purr-data-w64-build-log-Innosetup errors.sh

@alfonso.santimone Hm, I'm actually not sure if libdl.dll is needed in the Windows install. The dynamic loader should be using the Windows API. So you can try commenting that one out (line 115 of packages/win32_inno/Makefile).

@jancsika Thanks. Commented out that line but still errors purr-data-w64-build-log-Further Innosetup errors.sh
There's a lor of stuff called from c/WINDOWS/SysWOW64/ where usally all 32 libs stuff are living.
Given the huge complexity of the Purr Data project and my little confindence with the gcc and g++ compiler and makefiles is difficult to me to understand what's used for what.

Probably a more easy way to go would be to build PD vanilla for win64 (Lucas build works just ok) and then try to compile all the needed libraries for Win64 and the custom Purr Data UI framwork...then pack a special distro for win64.
What do you think about?

@alfonso.santimone That's probably the wrong path for libgcc.

Is there any libgcc* in /mingw64/bin? What does find /mingw64 -name "libgcc*" give you?

@jancsika said:

find /mingw64 -name "libgcc*"

fremen@fremenCPU MINGW64 ~
$ find /mingw64 -name "libgcc*"
/mingw64/bin/libgcc_s_seh-1.dll
/mingw64/lib/gcc/x86_64-w64-mingw32/6.2.0/libgcc.a
/mingw64/lib/gcc/x86_64-w64-mingw32/6.2.0/libgcc_eh.a
/mingw64/lib/gcc/x86_64-w64-mingw32/6.2.0/libgcc_s.a

@alfonso.santimone Try using /mingw64/bin/libgcc_s_seh-1.dll in the Makefile and see what happens

@jancsika in wich makefile?

@jancsika latest attempt ..still errors
purr-data-w64-build-log-Errors.sh

@alfonso.santimone said:

@jancsika in wich makefile?

purr-data/packages/win32_inno/Makefile

@alfonso.santimone said:

@jancsika latest attempt ..still errors
purr-data-w64-build-log-Errors.sh

I'm confused. You wrote about that you were excluding Gem, but it appears you are trying to build Gem.

@jancsika Yeah. I did a clean git repo cloning so i missed to comment out everything in lines 144-167 in purr-data/externals/Makefile, then now i commentig out lines 134-138 in purr-data/packages/win32_inno/Makefile and adding always in purr-data/packages/win32_inno/Makefile at line 147
install -p $(bin_src)/libgcc_s_seh-1.dll $(DESTDIR)$(bindir)
...report as soon as building process will end.