http://en.wikipedia.org/wiki/Microsoft_ ... s_for_UNIX
http://en.wikipedia.org/wiki/Interix
Perhaps we can make our engines fully compliant with Windows and UNIX by using only POSIX code?
Moderator: Andres Valverde
Threads, Signals, Sockets, ect. True you'll only have to write it once but it'd be much easier in my opinion to develop with one particular set of libraries.Onno Garms wrote:When starting a new project, it is nice to implement the system functions only once. In a running project, I don't see a reason to change them. I need different implementations for timer access and for non-blocking keyboard query. (Anything else, anybody?) Those are nicely wrapped and it's unlikely they ever need to be revisited.
It comes with Vista and you can download it for Windows XP for free I think.What license and what costs do Microsoft Windows Services for UNIX have?
I develop on Unix. The first transfer to windows was using Cygwin. In the meantime, I replaced Cygwin by native Windows functions to get rid of the GPL'ed cygwin1.dll. But note that
- There is a commercial cygwin license available (Does anybody know its price?)
- For those who plan to go open source with the GPL, Cygwin is a free alternative
Pradu wrote:Threads, Signals, Sockets, ect.
I don't at the moment but I might. Perhaps for things like specialized ICS support.Onno Garms wrote:Pradu wrote:Threads, Signals, Sockets, ect.
OK, I don't have threads yet. I thought about using the boost thread library. Why do you need signals and sockets in your engine?
Return to Programming and Technical Discussions
Users browsing this forum: No registered users and 4 guests