@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.exe

win32_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

1. some path adjusting
2. some file name adjusting
3. correct target architecture
4. invoke correct .dll libraries
5. Solve Gem issues not compiling for Win64
6. Solve fluidsynth~ issues not compiling for Win64

some good additions could be

1. new cyclone library
2. pd-else library
3. oFelia library
4. aubio library

@jancsika

Some report after testing Purr Data compiled for Win64.

1. 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

2. 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.

3. 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~

4. timestretch~ just crash Purr Data and the program quits.

5. moocow folder is empty

6. pixelTango does not work but i guess it has something to do with Gem externals dependencies

7. SMLib help file is not present

8. pmpd loads but does not seem to work

9. 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

1. some path adjusting
2. some file name adjusting
3. correct target architecture
4. invoke correct .dll libraries
5. Solve Gem issues not compiling for Win64
6. 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

1. a merge request on git.purrdata.net, or
2. 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.

@jancsika Yeah, i'll try today or tomorrow to sum up all changes i've done.
How the merge request work?
I mean, i commented out some crossplatform stuff to exclude Gem. So i don't want to do something that can harm the whole building system.

@alfonso.santimone said:

@jancsika Yeah, i'll try today or tomorrow to sum up all changes i've done.
How the merge request work?
I mean, i commented out some crossplatform stuff to exclude Gem. So i don't want to do something that can harm the whole building system.

Rather than comment them out in the merge request, write in the merge description the names of the libraries you had to exclude. We've got a "make light" recipe that can build without externals-- that should work with win64.

The Makefile changes need to have some conditionals in them to support both archs, but I (or someone else) can do those as long as you have all the changes needed to get a working Purr Data core on Win64.

@jancsika I wrote a .txt with alle the instructions to have a working building process for Win64. Building Purr Data for Windows 64bit.txt
Maybe you can just upload it in the page where the Win32 instructions are?
There are some change in the purr-data/externals/Makefile and several changes in the purr-data/packages/win32_inno/Makefile

@alfonso.santimone Great. I'll go through and see what changes need to be made to the Makefile to make it work correctly with both 32 and 64 bit archs.

@jancsika Let me know if you need any help! Meanwhile i'm trying to take a little confidence with make and gcc/g++ ( i'm more used to VS and CodeBlocks).

@alfonso.santimone Try this branch:

https://git.purrdata.net/jwilkes/purr-data/merge_requests/108

You should be able to successfully build the core with that. Let me know if there are any issues with it.

If that works ok I'll have a look at fluid~ and some of the other libs that don't yet build on win64.

@jancsika How can i try it? I don't know how to select this branch for compiling

@alfonso.santimone Click the button with the label "Check out branch." The follow the instructions in step 1.

@jancsika I followed step 1 (but before i deleted all my old purr-data build) and i have this
purr-data-light-win64-branch-build-log.sh

@jancsika , I installed Purr data 2.5.1 via agraef PPA in Xubuntu 18.04 and Ubuntu 18.04 LTS, in all two instalations I have visual glitches with all fonts:

Can I make something to solve this little anoying issue?

Thanks a lot for your work!!

That's really odd.

I'll have a look.