[PD-dev] cygwin port?

[cdr]

On Mon, Sep 13, 2004 at 12:15:51PM +0200, Reini Urban wrote:
> Nobody looked so far at a cygwin port?

besides ideological issues, NT kernel only misses shmget() stuff and fork(). just add a few #define or rewrite a few lines is all it takes to avoid the 75% overhead of cygwin,,

well SDL doesnt support video input (yet?) so on NT you are output-only if you build pdp or gridflow - maybe you're interested in developing some sort of abstracted directshow input-layer to be hooked into pdp and gridflow all at once - theres possibly-useful code in GEM already.

> I see various build targets, which would help.
> pd_cygwin would be a merge of pd_linux and some pd_nt (just the dllext 
> and some makefile additions, using a newer libtool to use dlltool and 
> maybe dllwrap)
> FYI, cygwin supports OOTB tcl/tk (native nt) and opengl (native or x11).
> And sound should be possible also in a mixture of linux and nt manner 
> (/dev/dsp wrappers and WinAPI).

install msysDTK (autoconf/CVS/openSSH/perl) and a shortcut like: C:\m\bin\rxvt.exe -fn "lucida console-10" -sl 10000 -e bash --login -i and you should see why cygwin isnt necessary - if you want to make a dpkg repository, that would be great..it is annoying to grab source from 50 places, reminds me of slackware..,

>
> The packaging would be similar to debian.
> I'd prefer cygwin over MSVC, or at least mingw. But if you already 
> support MSVC, mingw is straightforward.
> 
> when is cvs.sf.net populated? I prefer to update from cvs, than from 
> tar.gz. I miss gem, extensions, ...
> 
> It would be nice to have this finished for the convention.
> I'm already thinking of maintaining apache, php and postgresql for 
> cygwin, so puredata would be not so problematic to maintain for me, 
> compared to the others.

co -r devel_0_37 pd, use makefile.mingw. it is stil not in configure.in, if you feel like taking a stab at that..