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
-
Purr Data 2.5.0
-
@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 latest attempt ..still errors
purr-data-w64-build-log-Errors.shI'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. -
Is there a way to clean all the dirs to do a clean build?
-
@jancsika Ok so. no more Gem related errors...still innosetup errors.
Purr Data - Win64 Build Log April 09 2018 .sh -
@alfonso.santimone said:
@jancsika Ok so. no more Gem related errors...still innosetup errors.
Purr Data - Win64 Build Log April 09 2018 .shinstall: cannot stat '/mingw64/bin/libgcc_s_dw2-1.dll': No such file or directory
You have to replace that path with
/mingw64/bin/libgcc_s_seh-1.dll
-
@jancsika Thanks. Now building seems to be ok
Successful compile (177.719 sec). Resulting Setup program filename is:
C:\purr-data\packages\win32_inno\Output\Purr Data 2.5.0-20180404-rev.ff8afc1.exewin32_inno install succeeded!
copying pd-l2ork-specific externals...
done with l2ork addons.
done.But C:\purr-data\packages\win32_inno\Output\ is empty. I try to recompile tomorrow running MSYS2 in administrator mode because could be that Win10 doesn't like tho write files in the root directory. I'm not sure but could be. I'll check it tomorrow! Thanks for your help.
-
@alfonso.santimone Look in
purr-data/
. There should be an installer file there. -
@jancsika Yeah! that's true. So installed and working correctly at least with simple MIDI and audio test. Portaudio ASIO working. Now i'll check some external helpfile.
So i guess the only things to work on various Makefiles are- some path adjusting
- some file name adjusting
- correct target architecture
- invoke correct .dll libraries
- Solve Gem issues not compiling for Win64
- Solve fluidsynth~ issues not compiling for Win64
some good additions could be
- new cyclone library
- pd-else library
- oFelia library
- aubio library
-
Some report after testing Purr Data compiled for Win64.
-
I have a strange bug related to MIDI device. I'll have to check if it exists in PD vanilla 32 bit. I have the same bug in PD vanilla for 64bit compiled by Lucas. I don't think it is a multiclient midi driver issue. But i'll check it better. BTW if i choose a MIDI device and apply so it goes saved for the next start of Purr Data..well Purr Data doesn't start anymore and i have to clean the prefs via regedit because it seems that a command line pd.exe -nomidi does not work for Purr Data as it does with Vanilla
-
zexy library does not work even if the .dll externals files are compiled. I have to check the build log because i remember there were some red warnings about specific zexy externals. So every zexy help file i tried shows red outlined externals because the zexy stuff can't be instantiated.
-
there are minor naming errors in some help files that i guess are in the official Purr Data 32bit release (i.e. linearpan~ in pan lib should be linear_pan~
-
timestretch~ just crash Purr Data and the program quits.
-
moocow folder is empty
-
pixelTango does not work but i guess it has something to do with Gem externals dependencies
-
SMLib help file is not present
-
pmpd loads but does not seem to work
-
Gem and fluidsynth~ don't compile for win64 target (so as you know i removed those from the building process)
-
-
@alfonso.santimone said:
@jancsika Yeah! that's true. So installed and working correctly at least with simple MIDI and audio test. Portaudio ASIO working. Now i'll check some external helpfile.
So i guess the only things to work on various Makefiles are- some path adjusting
- some file name adjusting
- correct target architecture
- invoke correct .dll libraries
- Solve Gem issues not compiling for Win64
- Solve fluidsynth~ issues not compiling for Win64
Now that it is compiling and installing, would you mind wrapping up all the changes you made here to get it to build and submitting either
- a merge request on git.purrdata.net, or
- opening an issue here:
https://git.purrdata.net/jwilkes/purr-data/issues
Again, I just need to know the changes you made to get it into a working state.
Once these changes are merged we should be able to at least do a "light" build. Then we can focus on getting the rest of the libraries working, the midi issue, etc.