Great! A final thought. Maybe the Debian/Ubuntu-specific mxe requirements in the form of package manager commands could be totally removed and the link to the mxe requirements page could be provided instead for all cases ( http://mxe.cc/#requirements ). That would solve a couple of issues.
On Thu, Jun 11, 2015 at 9:03 PM, Steve Boyer <boyer.st...@gmail.com> wrote: > Harry, > > Those packages aren't required by mxe. I added them while testing, and > they persisted. I'll make note to remove those. > > As for the 64 bit version, it seems to be breaking at compiling the gui. > I'll mail out the error I'm getting when I'm next at my computer. > > Steve > On Jun 11, 2015 1:32 PM, "Harry Nakos" <xna...@gmail.com> 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, which is probably what you need. Can >> you try to follow this guide and see if there are packages missing >> afterwards? >> >> 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. 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 [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]) >>>> >> 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 [1] >>>> >>> _______________________________________________ >>>> >>> Hydrogen-devel mailing list >>>> >>> Hydrogen-devel@lists.sourceforge.net >>>> >>> https://lists.sourceforge.net/lists/listinfo/hydrogen-devel [2] >>>> >> >>>> >> -- >>>> >> >>>> >> follow me on my Audio & Linux blog >>>> >> <http://audio-and-linux.blogspot.com/ [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 [1] >>>> >> _______________________________________________ >>>> >> Hydrogen-devel mailing list >>>> >> Hydrogen-devel@lists.sourceforge.net >>>> >> https://lists.sourceforge.net/lists/listinfo/hydrogen-devel [2] >>>> > >>>> > >>>> > >>>> > Links: >>>> > ------ >>>> > [1] http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >>>> > [2] https://lists.sourceforge.net/lists/listinfo/hydrogen-devel >>>> > [3] >>>> > https://github.com/hydrogen-music/hydrogen/wiki/Packaging-for-Windows >>>> > [4] http://audio-and-linux.blogspot.com/ >>>> > [5] https://github.com/mikotoiii/hydrogen/blob/master/win32/README.md >>>> > >>>> > >>>> ------------------------------------------------------------------------------ >>>> > >>>> > _______________________________________________ >>>> > 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
