[Date Prev] [Date Index] [Date Next] [Thread Prev] [Thread Index] [Thread Next]
Bryan Stansell bryan@conserver.com
Fri, 31 Mar 2006 08:05:09 -0800 (PST)
On Fri, Mar 31, 2006 at 10:49:02AM -0500, Christopher Fowler wrote: > available to our customers. You do not need the Cygwin environment. > You only need the dll. So I created a zip file that contained > console.exe and cygwin?.dll. It worked fine on the cmd.com prompt. and this should work with 8.x.x as well. you might need to compile things with '--with-port=XXX' so that an /etc/services lookup isn't needed, but aside from that, i don't see why dropping console.exe and cygwin1.dll in a directory and running it won't work. haven't tried, however (i have a small development cygwin environment on my laptop). the exception to this might be if you compile with ssl or other extra libraries...the might require extra things to distribute. as for the education issue, well, perhaps it's just not right for your environment. i would make the claim that conserver would be right for *any* environment since it allows for logging (so you can go back and see what was wrong) and cooperative work on a single console. just those two features alone (not to mention the many others) make it worth the effort in my book. but, work habits and a willingness for change can be a long, hard battle, so you should obviously do what you feel is right. sure would be entertaining to at least have a native console binary for windows...that would help ease everyone's pain. who knows how tricky that'll be, though (i'm no windows programmer, that's for sure). Bryan