I support both. While cygwin has a large community of developers and users, when I build/link UWIN with my project, it outperforms the cygwin by several orders of magnitude. I also find the dos terminal compatibility better and external dependencies more manageable. I am also able to build a DLL for linking with Visual Studio via UWIN, and I can't do that, practically, with cygwin. There is a hack, but it's quite a hack and very fragile.
That's my experience anyway … ; ) … On 2013-04-25, at 11:39 AM, Simon Toedt <[email protected]> wrote: > On Thu, Apr 25, 2013 at 4:24 PM, Bear Limvere > <[email protected]> wrote: >> On 25-Apr-13 5:34, Sebastian Feld wrote: >>> >>> On Tue, Apr 16, 2013 at 10:22 PM, Bear Limvere >>> <[email protected]> wrote: >>>> >>>> I just got a new 64-bit computer and installed Windows7 for business >>>> reasons. I have been a loyal UWIN user for years, and depend on it for >>>> many >>>> development tasks; especially on perl. >>>> >>>> The base package I installed was: uwin-base.2012-08-06.win32.i386-64.exe, >>>> along with uwin-dev.2012-08-06.win32.i386-64.exe >>>> >>>> When I tried to install either uwin-groff.2008-11-15.win32.i386 or >>>> uwin-perl-58.2005-11-04.win32.i386, I get an open command prompt with the >>>> message "cannot find UWIN registry keys" >>>> >>>> Otherwise UWIN seems to be working fine. What can I do to get perl and >>>> the >>>> roff packages installed??? >>> >>> Has anyone found a solution for this problem? >> >> Please help! I would hate to be forced into abandoning UWIN > > Is there still anyone left who didn't abandon UWIN? The UWIN lists are > pretty much like a desert when I compare it to the hundreds of posting > I get from the Cygwin lists > > Simon > _______________________________________________ > uwin-users mailing list > [email protected] > http://lists.research.att.com/mailman/listinfo/uwin-users _______________________________________________ uwin-users mailing list [email protected] http://lists.research.att.com/mailman/listinfo/uwin-users
