- MINGW OR CYGWIN .DLL
- MINGW OR CYGWIN SOFTWARE
- MINGW OR CYGWIN CODE
- MINGW OR CYGWIN LICENSE
- MINGW OR CYGWIN FREE
But, this task can be simplified by using cross-platform toolkits or frameworks that allow coding once and having your code compile successfully for any platform.
MINGW OR CYGWIN SOFTWARE
It may be possible in some cases to use MinGW to compile something that was intended for compiling with Microsoft Visual C++ without too many modifications.Įven though MingW includes some header files and interface code allowing your code to interact with the Windows API, as with the regular standard libraries this doesn't impose licensing restrictions on software you have created.įor any non-trivial software application, such as one that uses a graphical interface, multimedia or accesses devices on the system, you leave the boundary of what Cygwin can do for you and further work will be needed to make your code cross-platform.
MINGW OR CYGWIN FREE
MinGW is a free and open source alternative to using the Microsoft Visual C++ compiler and its associated linking/make tools on Windows.
MINGW OR CYGWIN .DLL
dll files, though you could also cross-compile with the right settings, since you are basically using the GNU compiler tools suite. By default, code compiled in MinGW's GCC will compile to a native Windows X86 target, including. It also includes header files allowing the use of Windows' native API in your code.Īs a result your application needs to specifically be programmed for Windows, using the Windows API, which may mean significant alteration if it was created to rely on being run in a standard Unix environment and use Unix-specific features. It does not attempt to emulate or provide comprehensive compatibility with Unix, other that to provide a version of the GNU Compiler Collection, GNU Binutils and GNU Debugger that can be used natively in Windows. MinGW aims to simply be a port of GNU's development tools for Windows.
MINGW OR CYGWIN LICENSE
Even just linking your software with it, but distributing the dll separately, can still impose license restrictions on your code. You may distribute this with your software, but your software will have to comply with its open source license. When you distribute your software, the recipient will need to run it along with the Cygwin run-time environment (provided by the file cygwin1.dll). If you have existing source code that uses these interfaces, you may be able to compile it for use with Cygwin after making very few or even no changes, greatly simplifying the process of porting simple IO based Unix code for use on Windows. Try making a window with raw XLib code vs using the Win32 code, the difference is huge (And that is the correct comparison, mentioning the GTK or QT is not a direct comparison.) Win32 code, while slightly opaque, is miles easier to write then xlib code.Compile something in Cygwin and you are compiling it for Cygwin.Ĭompile something in MinGW and you are compiling it for Windows.Ĭygwin is a compatibility layer that makes it easy to port simple Unix-based applications to Windows, by emulating many of the basic interfaces that Unix-based operating systems provide, such as pipes, Unix-style file and directory access, and so on as documented by the POSIX standards. Truth be told, I actually prefer a lot of the win32 API OS calls over the GNU calls. There is NO ansi C++ standard for OS interaction (well, threading is going to be part of the standard here soon, but that's a bit off topic). When you run into specific problems is when you start to try playing with OS specific stuff (playing sound, making windows, ect). I've done some pretty intense programming and dealt with some pretty low level code, honestly, either compiler is going to do everything you need it to do, I doubt that you will ever run into a huge life altering difference between the two (so long as you don't do GNU/microsoft specific code.)
The microsoft Visual C++ compiler is pretty good about Ansi standards, thus most code that compiles with Mingw compiles with microsofts compiler without many issues.Īs nothing man said, if you want a linux environment (GNU libc stuff) then you probably should just do a linux VM. MingW = lets keep unix out of windows as much as possible, us as much native windows stuff as possible.Ĭygwin is usually a little bit slower because it adds a couple of extra layers, where as mingw is generally pretty good about doing the bare minimum of stuff.Īs for the "bunch of Microsoft specific libraries of VCC.", you only use those libraries if you want to. Cygwin = lets put unix on windows, use as much native unix stuff as possible
0 kommentar(er)
