Hey, So the current status is that my last cross compile was successful. I was just waiting for Sebastien to review the last batch of changes before they were pulled in.
It will still only compile 32bit though, someone was having a look to see about making some changes to the source to allow it to compile 64bit (there was a problem with the ints not being int ints if I recall, which made the compile fail due to incorrect type being set). Steve On Aug 10, 2015 4:51 AM, "Thijs van severen" <thijsvanseve...@gmail.com> wrote: > Hi guys > > i'm going trough all the open github tickets and some of theme are windows > related (or have to do with the fact that the last windows version is > outdated) > my guess is that most windows tickets will be closed as soon as we have an > up to date version (so all eyes are on you ;-) > > can you share the current status with us ? > > thanks for all the hard work on this !! > > grtz > Thijs > > > > 2015-06-18 2:34 GMT+02:00 Steve Boyer <boyer.st...@gmail.com>: > >> Yeah definitely interesting, I noticed the portaudio header in the jack >> source when I initially ran into the problems getting hydrogen to compile >> with jack support, which is why I was able to track it down so fast (I was >> looking to see if there was an easy way not using code blocks to compile it >> to get the dll and headers so we wouldn't have to copy them from Windows). >> Removal of the portaudio stuff might be able to be proposed upstream. >> >> I'll try the force remake of portaudio here in the morning. But I reckon >> that it should work. I can build the recompile of portaudio into my script >> if it doesn't get a different fix soon. >> >> Steve >> >> On Wed, Jun 17, 2015, 20:07 Harry Nakos <xna...@gmail.com> wrote: >> >>> Really, really, really interesting... Indeed. From mxe/log/jack I see: >>> >>> + install >>> /home/xnakos/Projects/mxe/usr/i686-w64-mingw32.shared/lib/libportaudio.dll.a >>> (from build/windows/libportaudio.dll.a) >>> >>> To work around this (do not still know the implications), I went to >>> mxe/src/portaudio.mk and added this (random dependency to force >>> re-make, I am not aware of a way to force re-make a package other than >>> adding a dependency or in general changing the MK file (maybe)): >>> >>> $(PKG)_DEPS := gcc jack >>> >>> in order to be able to make portaudio again. After that compilation of >>> hydrogen is successful. You can try it and tell me what happens. It is not >>> more than 24 hours ago that my jack commits were pulled into mxe. I now saw >>> that jack2 contains an ancient header file of portaudio for windows... I >>> guess I will look into that. >>> >>> Harry >>> >>> On Wed, Jun 17, 2015 at 6:51 PM, Steve Boyer <boyer.st...@gmail.com> >>> wrote: >>> >>>> Hey Harry, >>>> >>>> So I spent most of this morning building a fresh mxe to test in, and >>>> here are the results: Hydrogen fails to build, hitting an error on >>>> libhydrogen-core-0.9.7 on portaudio stuff. >>>> I believe that this is due to jack patching some of the portaudio >>>> files. Here's details for the error. >>>> >>>> sboyer@pc16:/home/sboyer/build/hydrogen/source$ make >>>> Linking CXX shared library libhydrogen-core-0.9.7.dll >>>> CMakeFiles/hydrogen-core-0.9.7.dir/objects.a(portaudio_driver.cpp.obj): >>>> In function `ZN6H2Core15PortAudioDriver10disconnectEv': >>>> /home/local/NBIB/sboyer/build/hydrogen/source/src/core/src/IO/portaudio_driver.cpp:107: >>>> undefined reference to `Pa_StopStream' >>>> /home/local/NBIB/sboyer/build/hydrogen/source/src/core/src/IO/portaudio_driver.cpp:114: >>>> undefined reference to `Pa_CloseStream' >>>> /home/local/NBIB/sboyer/build/hydrogen/source/src/core/src/IO/portaudio_driver.cpp:121: >>>> undefined reference to `Pa_Terminate' >>>> /home/local/NBIB/sboyer/build/hydrogen/source/src/core/src/IO/portaudio_driver.cpp:111: >>>> undefined reference to `Pa_GetErrorText' >>>> /home/local/NBIB/sboyer/build/hydrogen/source/src/core/src/IO/portaudio_driver.cpp:118: >>>> undefined reference to `Pa_GetErrorText' >>>> CMakeFiles/hydrogen-core-0.9.7.dir/objects.a(portaudio_driver.cpp.obj): >>>> In function `ZN6H2Core15PortAudioDriver7connectEv': >>>> /home/local/NBIB/sboyer/build/hydrogen/source/src/core/src/IO/portaudio_driver.cpp:71: >>>> undefined reference to `Pa_Initialize' >>>> /home/local/NBIB/sboyer/build/hydrogen/source/src/core/src/IO/portaudio_driver.cpp:75: >>>> undefined reference to `Pa_GetErrorText' >>>> /home/local/NBIB/sboyer/build/hydrogen/source/src/core/src/IO/portaudio_driver.cpp:87: >>>> undefined reference to `Pa_OpenDefaultStream' >>>> /home/local/NBIB/sboyer/build/hydrogen/source/src/core/src/IO/portaudio_driver.cpp:91: >>>> undefined reference to `Pa_GetErrorText' >>>> /home/local/NBIB/sboyer/build/hydrogen/source/src/core/src/IO/portaudio_driver.cpp:95: >>>> undefined reference to `Pa_StartStream' >>>> /home/local/NBIB/sboyer/build/hydrogen/source/src/core/src/IO/portaudio_driver.cpp:99: >>>> undefined reference to `Pa_GetErrorText' >>>> collect2: error: ld returned 1 exit status >>>> src/core/CMakeFiles/hydrogen-core-0.9.7.dir/build.make:1422: recipe for >>>> target 'src/core/libhydrogen-core-0.9.7.dll' failed >>>> make[2]: *** [src/core/libhydrogen-core-0.9.7.dll] Error 1 >>>> CMakeFiles/Makefile2:137: recipe for target >>>> 'src/core/CMakeFiles/hydrogen-core-0.9.7.dir/all' failed >>>> make[1]: *** [src/core/CMakeFiles/hydrogen-core-0.9.7.dir/all] Error 2 >>>> Makefile:137: recipe for target 'all' failed >>>> make: *** [all] Error 2 >>>> >>>> >>>> sboyer@pc16:/opt/mxe/usr$ diff -r i686-w64-mingw32.shared/ >>>> /opt/mxe.hydrogen/usr/i686-w64-mingw32.shared/ | grep portaudio >>>> Binary files i686-w64-mingw32.shared/bin/libportaudio-2.dll and >>>> /opt/mxe.hydrogen/usr/i686-w64-mingw32.shared/bin/libportaudio-2.dll differ >>>> Binary files i686-w64-mingw32.shared/bin/test-portaudio.exe and >>>> /opt/mxe.hydrogen/usr/i686-w64-mingw32.shared/bin/test-portaudio.exe differ >>>> Binary files i686-w64-mingw32.shared/lib/libportaudio.dll.a and >>>> /opt/mxe.hydrogen/usr/i686-w64-mingw32.shared/lib/libportaudio.dll.a differ >>>> >>>> On Wed, Jun 17, 2015 at 8:18 AM Steve Boyer <boyer.st...@gmail.com> >>>> wrote: >>>> >>>>> Hey Harry, >>>>> That would simplify things greatly. >>>>> I will give it a go shortly, and report back. Thanks for the heads up. >>>>> >>>>> Steve >>>>> On Jun 17, 2015 7:36 AM, "Harry Nakos" <xna...@gmail.com> wrote: >>>>> >>>>>> Steve, hi! >>>>>> >>>>>> MXE is now capable of making jack! I hope at least! Could you try it >>>>>> by adding jack to the make list and removing manual inclusion of header >>>>>> files from the script? It will simplify some things I hope. >>>>>> >>>>>> Harry >>>>>> >>>>>> On Tue, Jun 16, 2015 at 9:56 PM, Steve Boyer <boyer.st...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> Hey Sebastian, >>>>>>> >>>>>>> I have pushed my new version of the script up. The major changes in >>>>>>> it are as follows: >>>>>>> cross_compile.sh - now only builds hydrogen and gets the required >>>>>>> files for a Windows release (includes the jack installer, and the >>>>>>> Windows >>>>>>> installer for ladspa plugins). >>>>>>> mxe_installer.sh - I went through the mxe requirements page and did >>>>>>> up a quick script to hopefully install mxe on any of the listed systems >>>>>>> (OS >>>>>>> X included). I only have a Debian system to test this on, so I can't >>>>>>> confirm that the script will work well on any other systems (anyone >>>>>>> want to >>>>>>> test?). I also added references to the requirements page and the >>>>>>> tutorial >>>>>>> page inside the script to point people to where they should look if >>>>>>> anything goes wrong. >>>>>>> The MXE check now checks for the cmake toolchain file used by mxe to >>>>>>> determine if mxe is installed, both in the mxe_installer.sh and >>>>>>> cross_compile.sh scripts. If you can think of a better way to check for >>>>>>> mxe's existence then I'd be happy implementing that. >>>>>>> >>>>>>> Steve >>>>>>> >>>>>>> On Mon, Jun 15, 2015 at 5:13 PM <mau...@smoors.de> wrote: >>>>>>> >>>>>>>> Hi Harry, hi Steve! >>>>>>>> >>>>>>>> On 2015-06-11 18:32, Harry Nakos wrote: >>>>>>>> > Hi, guys! >>>>>>>> > >>>>>>>> > Sebastian, there is already a link in the Readme.md for compiling >>>>>>>> the >>>>>>>> > cross-compiler on other Unix systems, which in turn links to >>>>>>>> > http://mxe.cc/#requirements-macos [7], which is probably what you >>>>>>>> > need. Can you try to follow this guide and see if there are >>>>>>>> packages >>>>>>>> > missing afterwards? >>>>>>>> >>>>>>>> That looks quite helpful! I will see if i can get sth. working after >>>>>>>> Steve has pushed the next version of his script. But i think will >>>>>>>> give >>>>>>>> testing on linux definitely the priority. In my opionion it is >>>>>>>> better to >>>>>>>> concentrate on one platform first :) >>>>>>>> >>>>>>>> Best Regards, >>>>>>>> >>>>>>>> Sebastian >>>>>>>> >>>>>>>> > Steve, great job once again! I haven't had to time to try it yet. >>>>>>>> A >>>>>>>> > few observations/questions. Why are libfftw3-dev and >>>>>>>> libportaudio-dev >>>>>>>> > in mxe's requirements? Are these needed at all for the >>>>>>>> > cross-compilation? If there are extra requirements for some reason >>>>>>>> > (what am I missing?), I believe they should be listed separately >>>>>>>> (from >>>>>>>> > the mxe requirements). On another topic, I believe that the path >>>>>>>> to >>>>>>>> > mxe should not be taken for granted or hardcoded. /opt requires >>>>>>>> root >>>>>>>> > privileges to be written for one. The script could require an >>>>>>>> > environment variable to be set, one that would have the path to >>>>>>>> mxe >>>>>>>> > assigned to it. Or the script could take the path to mxe as an >>>>>>>> > argument. I believe the environment variable before invoking the >>>>>>>> > script would be a better option (simpler) though. About the 64-bit >>>>>>>> > version, what problem do you face? Make sure that all packages >>>>>>>> > required are available for 64-bit by mxe. >>>>>>>> > >>>>>>>> > Harry >>>>>>>> > >>>>>>>> > On Thu, Jun 11, 2015 at 12:09 AM, Steve Boyer < >>>>>>>> boyer.st...@gmail.com> >>>>>>>> > wrote: >>>>>>>> > >>>>>>>> >> Hey Sebastian, >>>>>>>> >> >>>>>>>> >> I was actually going to remove my pull and submit a new one. I've >>>>>>>> >> changed how the system packages the installer (using CPack now >>>>>>>> >> instead of straight NSIS. I'll have to update the documentation >>>>>>>> to >>>>>>>> >> reflect the changes for non Debian systems (if you'd like to >>>>>>>> tell me >>>>>>>> >> the required packages on Mac I'd be more then happy to add Mac >>>>>>>> >> support to the cross building (unfortunately I don't have a Mac >>>>>>>> to >>>>>>>> >> test on, and am unfamiliar with the packaging system). >>>>>>>> >> >>>>>>>> >> All my checks are pretty loose so I should definitely tighten up >>>>>>>> and >>>>>>>> >> test those a little better. The specific mxe problem you listed >>>>>>>> has >>>>>>>> >> sort of been fixed since I discovered during testing that if you >>>>>>>> >> compile mxe in your build dir, you need to do an awful lot to >>>>>>>> get it >>>>>>>> >> to work once moved to /opt. So now it builds in and checks >>>>>>>> against >>>>>>>> >> /opt/mxe. I'll tighten up the checks for some of the >>>>>>>> requirements of >>>>>>>> >> mxe before setting it as installed in my new version. >>>>>>>> >> >>>>>>>> >> With the cleanup I did for the experimental 64bit windows >>>>>>>> version, I >>>>>>>> >> obsoleted some of the code in the script file, and was thinking >>>>>>>> >> about building an mxe installer as a separate item. >>>>>>>> Unfortunately I >>>>>>>> >> haven't gotten the 64bit version to compile just yet but it's a >>>>>>>> work >>>>>>>> >> in progress. >>>>>>>> >> >>>>>>>> >> My readme file has become a little outdated but I plan on >>>>>>>> updating >>>>>>>> >> it with the proper manual steps. As well as a brief description >>>>>>>> of >>>>>>>> >> the options in the script. I will need to do this because the >>>>>>>> build >>>>>>>> >> structure has changed since CPack wanted to include everything in >>>>>>>> >> the package, and wasn't moving the exe and dll files to the >>>>>>>> proper >>>>>>>> >> locations, and when I'd move the source tree into a sub directory >>>>>>>> >> using CPack everything would break. >>>>>>>> >> >>>>>>>> >> The new structure is build/hydrogen git clone hydrogen then >>>>>>>> rename >>>>>>>> >> hydrogen to source and build in the project dir. With this change >>>>>>>> >> though I was required to do some linking as CPack was complaining >>>>>>>> >> about absolute paths. >>>>>>>> >> >>>>>>>> >> Hopefully I'll have a better version of everything by next week >>>>>>>> >> sometime. In the meantime if you want to email me some of the Mac >>>>>>>> >> specific stuff I can build it into the script so you hopefully >>>>>>>> won't >>>>>>>> >> run into issues with the cross compile next time. >>>>>>>> >> >>>>>>>> >> Steve >>>>>>>> >> >>>>>>>> >> On Jun 10, 2015 5:45 PM, <mau...@smoors.de> wrote: >>>>>>>> >> >>>>>>>> >>> Hi Steve! >>>>>>>> >>> >>>>>>>> >>> That sounds awesome! I've started to try your scripts before >>>>>>>> >>> merging >>>>>>>> >>> them and run into the following issues: >>>>>>>> >>> >>>>>>>> >>> 1. Maybe you should note some general prerequisite in readme.md >>>>>>>> >>> [1]. Sth. >>>>>>>> >>> like "this works only on debian-based linux systems". Keep in >>>>>>>> >>> mind that >>>>>>>> >>> there are also people with OS X out there (eh,like me..) that >>>>>>>> may >>>>>>>> >>> think >>>>>>>> >>> they could cross-compile for windows :) >>>>>>>> >>> >>>>>>>> >>> 2. It would be great if you coud list the mxe requirements >>>>>>>> >>> somewhere or >>>>>>>> >>> see to it that your scripts install everything. In my case, the >>>>>>>> >>> packages >>>>>>>> >>> autopoint, bison, flex and gperf were missing. Related problem: >>>>>>>> >>> After >>>>>>>> >>> /opt/mxe is created, your script seems to think that mxe is >>>>>>>> >>> installed, >>>>>>>> >>> even if it failed to install. It only checks the directory >>>>>>>> >>> structure.. >>>>>>>> >>> In addition, it uses "mv" to place the directory structure in >>>>>>>> >>> /opt. If >>>>>>>> >>> you run the script again, the original source in the build dir >>>>>>>> is >>>>>>>> >>> not >>>>>>>> >>> found (because it got moved). Maybe "cp -r" would be better >>>>>>>> >>> suited >>>>>>>> >>> here.. >>>>>>>> >>> >>>>>>>> >>> This is were i stopped today, maybe i can give it a new try at >>>>>>>> >>> the >>>>>>>> >>> weekend! >>>>>>>> >>> >>>>>>>> >>> Best regards, >>>>>>>> >>> Sebastian >>>>>>>> >>> >>>>>>>> >>> On 2015-05-27 21:47, Steve Boyer wrote: >>>>>>>> >>>> I have an update from the Windows front. I was able to >>>>>>>> >>> cross-compile >>>>>>>> >>>> Hydrogen with jack support today, which brings the supported >>>>>>>> >>> drivers >>>>>>>> >>>> up to Jack and Portaudio (which I think is all Windows can >>>>>>>> >>> use). >>>>>>>> >>>> >>>>>>>> >>>> My setup is a Debian system using mxe to cross-compile for >>>>>>>> >>> Windows, >>>>>>>> >>>> and a Windows 7 system for testing. I've got most of my >>>>>>>> >>> documentation >>>>>>>> >>>> up to date in the README.md file in my fork, but my auto build >>>>>>>> >>> script >>>>>>>> >>>> has become rather outdated and I am going to expand upon it >>>>>>>> >>> anyway to >>>>>>>> >>>> allow you to have a permanent build environment set up instead >>>>>>>> >>> of the >>>>>>>> >>>> temporary one it makes currently, etc. >>>>>>>> >>>> >>>>>>>> >>>> The wiki outlines steps to compile hydrogen on Windows for >>>>>>>> >>> Windows, >>>>>>>> >>>> which I haven't tried yet but shouldn't be much different since >>>>>>>> >>> they >>>>>>>> >>>> both use mingw as the compiler. Once I get my script updated I >>>>>>>> >>> will >>>>>>>> >>>> start to tackle that. I may just move on to packaging with NSIS >>>>>>>> >>> though >>>>>>>> >>>> then come back to it. >>>>>>>> >>>> >>>>>>>> >>>> As it stands you might be able to update the wiki to add the up >>>>>>>> >>> to >>>>>>>> >>>> date cross compile instructions from the README.md file here: >>>>>>>> >>>> >>>>>>>> >>> >>>>>>>> https://github.com/mikotoiii/hydrogen/blob/master/win32/README.md >>>>>>>> >>> [2] [5] >>>>>>>> >>>> >>>>>>>> >>>> - Steve >>>>>>>> >>>> >>>>>>>> >>>> On Tue, May 26, 2015 at 4:58 AM, Thijs van severen >>>>>>>> >>>> <thijsvanseve...@gmail.com> wrote: >>>>>>>> >>>> >>>>>>>> >>>>> Hi Steve and welcome to the team ! >>>>>>>> >>>>> (sorry for the late reply :-S ) >>>>>>>> >>>>> >>>>>>>> >>>>> i assume that you already found your way to the wiki, and more >>>>>>>> >>>>> specifically the pages that describe the compilation/packaging >>>>>>>> >>> for >>>>>>>> >>>>> Windows >>>>>>>> >>>>> >>>>>>>> >>>> >>>>>>>> >>> >>>>>>>> >> >>>>>>>> > ( >>>>>>>> https://github.com/hydrogen-music/hydrogen/wiki/Packaging-for-Windows >>>>>>>> >>> [3] >>>>>>>> >>>>> [3]) >>>>>>>> >>>>> I'm pretty sure that the wiki is not up to date, so if you >>>>>>>> >>> find >>>>>>>> >>>>> anything that needs to be changed just let me know via this ML >>>>>>>> >>>>> >>>>>>>> >>>>> A lot of people will be grateful if you can find a way to >>>>>>>> >>> speed up >>>>>>>> >>>>> and simplify the compilation for windows, so good luck ! >>>>>>>> >>>>> >>>>>>>> >>>>> Grtz >>>>>>>> >>>>> Thijs >>>>>>>> >>>>> >>>>>>>> >>>>> 2015-05-22 16:20 GMT+02:00 Steve Boyer >>>>>>>> >>> <boyer.st...@gmail.com>: >>>>>>>> >>>>> >>>>>>>> >>>>>> Hey everyone, >>>>>>>> >>>>>> >>>>>>>> >>>>>> First I will introduce myself. My name is Steve aka >>>>>>>> >>> mikotoiii, and >>>>>>>> >>>>>> I've been using Hydrogen with my band for a little while now. >>>>>>>> >>> What >>>>>>>> >>>>>> sparked me to join and try to contribute was the progression >>>>>>>> >>> in >>>>>>>> >>>>>> Linux, but not in Windows. I am a sysadmin by trade, which >>>>>>>> >>> means >>>>>>>> >>>>>> that I compile and test software on a number of different >>>>>>>> >>> systems >>>>>>>> >>>>>> and platforms routinely. >>>>>>>> >>>>>> >>>>>>>> >>>>>> I should also state that I am not a programmer, though I do >>>>>>>> >>> know >>>>>>>> >>>>>> enough to get by to make small fixes to allow something to >>>>>>>> >>>>>> compile. I do have a lot of exposure to Linux, both from my >>>>>>>> >>> job >>>>>>>> >>>>>> and from my personal enthusiasm for it, and I am decent at >>>>>>>> >>>>>> scripting in it. >>>>>>>> >>>>>> >>>>>>>> >>>>>> What I would like to work on, and have been in my personal >>>>>>>> >>> fork so >>>>>>>> >>>>>> far is fixing up the compiling scripts and documentation for >>>>>>>> >>> the >>>>>>>> >>>>>> cross compiling of the Windows version (I have already >>>>>>>> >>> compiled >>>>>>>> >>>>>> 0.9.7 for Windows, and am currently testing it out), as well >>>>>>>> >>> as >>>>>>>> >>>>>> making a new compiling script to help speed up the process of >>>>>>>> >>>>>> cross compiling. >>>>>>>> >>>>>> >>>>>>>> >>>>>> I hope that I can help contribute to this project and bring >>>>>>>> >>> the >>>>>>>> >>>>>> Windows versions up to date >>>>>>>> >>>>>> >>>>>>>> >>>>>> Cheers, >>>>>>>> >>>>>> >>>>>>>> >>>>>> mikotoiii >>>>>>>> >>>>>> >>>>>>>> >>>>>> >>>>>>>> >>>>> >>>>>>>> >>>> >>>>>>>> >>> >>>>>>>> >> >>>>>>>> > >>>>>>>> ------------------------------------------------------------------------------ >>>>>>>> >>>>>> One dashboard for servers and applications across >>>>>>>> >>>>>> Physical-Virtual-Cloud >>>>>>>> >>>>>> Widest out-of-the-box monitoring support with 50+ >>>>>>>> >>> applications >>>>>>>> >>>>>> Performance metrics, stats and reports that give you >>>>>>>> >>> Actionable >>>>>>>> >>>>>> Insights >>>>>>>> >>>>>> Deep dive visibility with transaction tracing using APM >>>>>>>> >>> Insight. >>>>>>>> >>>>>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y [4] >>>>>>>> >>> [1] >>>>>>>> >>>>>> _______________________________________________ >>>>>>>> >>>>>> Hydrogen-devel mailing list >>>>>>>> >>>>>> Hydrogen-devel@lists.sourceforge.net >>>>>>>> >>>>>> https://lists.sourceforge.net/lists/listinfo/hydrogen-devel >>>>>>>> >>> [5] [2] >>>>>>>> >>>>> >>>>>>>> >>>>> -- >>>>>>>> >>>>> >>>>>>>> >>>>> follow me on my Audio & Linux blog >>>>>>>> >>>>> <http://audio-and-linux.blogspot.com/ [6] [4]> ! >>>>>>>> >>>>> >>>>>>>> >>>>> >>>>>>>> >>>> >>>>>>>> >>> >>>>>>>> >> >>>>>>>> > >>>>>>>> ------------------------------------------------------------------------------ >>>>>>>> >>>>> One dashboard for servers and applications across >>>>>>>> >>>>> Physical-Virtual-Cloud >>>>>>>> >>>>> Widest out-of-the-box monitoring support with 50+ applications >>>>>>>> >>>>> Performance metrics, stats and reports that give you >>>>>>>> >>> Actionable >>>>>>>> >>>>> Insights >>>>>>>> >>>>> Deep dive visibility with transaction tracing using APM >>>>>>>> >>> Insight. >>>>>>>> >>>>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y [4] >>>>>>>> >>> [1] >>>>>>>> >>>>> _______________________________________________ >>>>>>>> >>>>> Hydrogen-devel mailing list >>>>>>>> >>>>> Hydrogen-devel@lists.sourceforge.net >>>>>>>> >>>>> https://lists.sourceforge.net/lists/listinfo/hydrogen-devel >>>>>>>> >>> [5] [2] >>>>>>>> >>>> >>>>>>>> >>>> >>>>>>>> >>>> >>>>>>>> >>>> Links: >>>>>>>> >>>> ------ >>>>>>>> >>>> [1] http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >>>>>>>> [4] >>>>>>>> >>>> [2] >>>>>>>> https://lists.sourceforge.net/lists/listinfo/hydrogen-devel >>>>>>>> >>> [5] >>>>>>>> >>>> [3] >>>>>>>> >>>> >>>>>>>> >>> >>>>>>>> >> >>>>>>>> > >>>>>>>> https://github.com/hydrogen-music/hydrogen/wiki/Packaging-for-Windows >>>>>>>> >>> [3] >>>>>>>> >>>> [4] http://audio-and-linux.blogspot.com/ [6] >>>>>>>> >>>> [5] >>>>>>>> >>> >>>>>>>> https://github.com/mikotoiii/hydrogen/blob/master/win32/README.md >>>>>>>> >>> [2] >>>>>>>> >>>> >>>>>>>> >>>> >>>>>>>> >>> >>>>>>>> >> >>>>>>>> > >>>>>>>> ------------------------------------------------------------------------------ >>>>>>>> >>>> >>>>>>>> >>>> _______________________________________________ >>>>>>>> >>>> Hydrogen-devel mailing list >>>>>>>> >>>> Hydrogen-devel@lists.sourceforge.net >>>>>>>> >>>> https://lists.sourceforge.net/lists/listinfo/hydrogen-devel >>>>>>>> [5] >>>>>>>> >>> >>>>>>>> >>> >>>>>>>> >> >>>>>>>> > >>>>>>>> ------------------------------------------------------------------------------ >>>>>>>> >>> _______________________________________________ >>>>>>>> >>> Hydrogen-devel mailing list >>>>>>>> >>> Hydrogen-devel@lists.sourceforge.net >>>>>>>> >>> https://lists.sourceforge.net/lists/listinfo/hydrogen-devel [5] >>>>>>>> >> >>>>>>>> >> >>>>>>>> > >>>>>>>> ------------------------------------------------------------------------------ >>>>>>>> >> >>>>>>>> >> _______________________________________________ >>>>>>>> >> Hydrogen-devel mailing list >>>>>>>> >> Hydrogen-devel@lists.sourceforge.net >>>>>>>> >> https://lists.sourceforge.net/lists/listinfo/hydrogen-devel [5] >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > Links: >>>>>>>> > ------ >>>>>>>> > [1] http://readme.md >>>>>>>> > [2] >>>>>>>> https://github.com/mikotoiii/hydrogen/blob/master/win32/README.md >>>>>>>> > [3] >>>>>>>> > >>>>>>>> https://github.com/hydrogen-music/hydrogen/wiki/Packaging-for-Windows >>>>>>>> > [4] http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >>>>>>>> > [5] https://lists.sourceforge.net/lists/listinfo/hydrogen-devel >>>>>>>> > [6] http://audio-and-linux.blogspot.com/ >>>>>>>> > [7] http://mxe.cc/#requirements-macos >>>>>>>> > >>>>>>>> > >>>>>>>> ------------------------------------------------------------------------------ >>>>>>>> > >>>>>>>> > _______________________________________________ >>>>>>>> > Hydrogen-devel mailing list >>>>>>>> > Hydrogen-devel@lists.sourceforge.net >>>>>>>> > https://lists.sourceforge.net/lists/listinfo/hydrogen-devel >>>>>>>> >>>>>>>> >>>>>>>> ------------------------------------------------------------------------------ >>>>>>>> _______________________________________________ >>>>>>>> Hydrogen-devel mailing list >>>>>>>> Hydrogen-devel@lists.sourceforge.net >>>>>>>> https://lists.sourceforge.net/lists/listinfo/hydrogen-devel >>>>>>>> >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------------------------ >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Hydrogen-devel mailing list >>>>>>> Hydrogen-devel@lists.sourceforge.net >>>>>>> https://lists.sourceforge.net/lists/listinfo/hydrogen-devel >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> >>>>>> _______________________________________________ >>>>>> Hydrogen-devel mailing list >>>>>> Hydrogen-devel@lists.sourceforge.net >>>>>> https://lists.sourceforge.net/lists/listinfo/hydrogen-devel >>>>>> >>>>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> >>>> _______________________________________________ >>>> Hydrogen-devel mailing list >>>> Hydrogen-devel@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/hydrogen-devel >>>> >>>> >>> >>> ------------------------------------------------------------------------------ >>> _______________________________________________ >>> Hydrogen-devel mailing list >>> Hydrogen-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/hydrogen-devel >>> >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Hydrogen-devel mailing list >> Hydrogen-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/hydrogen-devel >> >> > > > -- > follow me on my Audio & Linux blog <http://audio-and-linux.blogspot.com/> > ! > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Hydrogen-devel mailing list > Hydrogen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/hydrogen-devel > >
------------------------------------------------------------------------------
_______________________________________________ Hydrogen-devel mailing list Hydrogen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
