So, I have a big C project that was completely built on Unix (SPARC Solaris). I and some others began to revise it, because they were interested in the assembly of windows.
none of us did this with a project of this size, so for beginners, someone ported something from unix to windows and could give me some pointers or how they did it.
our first step in our plan was to define the / dev compiler environment.
it seems that our options are MS Visual Studio, Cygwin, mingw / gcc and Windows Services for UNIX (SFU).
we are on a rather short schedule, so we want to rewrite as little code as possible.
So, the decision about the compiler.
Another problem is that the code really uses POSIX thread commands (pthread, etc.)
we would prefer to compile initially without using any layer between the executable and the OS. Unfortunately, with pthread calls in our code, this may not be possible.
I believe that both Cygwin and SFU do just that. Cygwin has a .dll that must be included in the compiled code for it to work. I'm not sure about SFU, any information about this would be greatly appreciated. This seemed like a good option, but was designed to allow the compiled UNIX software to run on a Windows machine with SFU, rather than some old window.
mingw has the ability to create custom exes, but does not support POSIX.
, - , , . - , , .