OK, CrossBridge uses unix tools like gcc and swig. So removing the cygwin requirement will be painful.
What is the current sentiment? Require Cygwin or Visual Studio? At least Cygwin is free. In theory other unix shells for Windows will work but CrossBridge doc onl mentions Cygwin. Meanwhile, I think I will look into why the CrossBridge code was so much faster. In theory the result is abc code. -Alex On 6/2/14 9:49 PM, "Alex Harui" <aha...@adobe.com> wrote: >Well, I'm new to Native Extensions as well, but it appears you can't >create a single extension that works on both OSX and Windows. Folks seem >to be using Visual Studio for Windows and Xcode for Mac. That seems like >a lot of work and a complicated build environment. The nice thing about >the CrossBridge code is that it can be one cross-platform project. I'm >going to look into where the cygwin dependencies are in CrossBridge and >see if they can be removed, unless someone knows of a way to simplify the >Native Extension development. > >-Alex > >On 6/2/14 2:35 PM, "Alex Harui" <aha...@adobe.com> wrote: > >>In theory, all PMC members with Windows computers have Cygwin or some >>shell script processor in place otherwise they cannot run Mustella. >> >>We could create a separate release package like we did for PixelBender, >>but seriously, how many of you are going to build the installer from >>sources? >> >>I'll look into a intel-only NativeExtension version of MD5 next. >> >>-Alex >> >>On 6/2/14 2:20 PM, "Michael A. Labriola" <labri...@digitalprimates.net> >>wrote: >> >>>> -1 for Cygwin too :-( >>> >>> >>>Something to note for Windows Users, if you install git bash (which is >>>generally part of the windows install for git) you can use it in place >>>of >>>Cygwin. It might be a much easier way for us to move forward instead of >>>requiring Cygwin. >>> >>>Mike >> >
