Time: 2003-06-08 often sees a lot of people from some places to treat DEV C as a compiler, and some subtle errors in the usage method are also found. So I want to talk about how to talk to my opinion on how to make good use of DEV C . This involves concept and consciousness, I think I have to brainwash my friends again.
DEV C is not a compiler
First of all, I hope that everyone will understand that DEV C itself only provides a simple graphical interface, which is not a complete development environment. If you want to develop software in this environment, GCC needs GCC to varies on Windows or Linux, such as MingW, Cygwin, DJGPP, etc. With these GCC-based development environments, plus the DEV C can constitute a complete open integrated development environment IDE. The charm of this combination is that although it will be subject to copyright and the license agreement, you don't have to pay a penny for these things.
Know GCC-based compiler
On Windows, we often use CygWin and MingW, while DJGPP variants are dominated by DOS, and they can be a strong core of DEV C . Usually their issuance does not only include a lot of utilities with a compiler environment. For example, packaging tools (TAR, GZIP), file comparison tools (DIFF, DIFF3), Patches (PATCH), Script Automatic Tools (AWK, BIONS), TexInfo ..., etc., there are many options. Only when we have these aids can we say that there is a complete development environment. (Excellent: Microsoft also launched a UNIX kit, Chinese information can be found in Microsoft Taiwan.)
Cygwin's development direction is the most likely to simulate UNIX POSIX on Windows, so the software compiled by this system basically needs Cygwin's POSIX analog module. The only exception, give the compiler to the -Mno-cygwin directive At the same time installed with the MINGW runtime library, you can directly generate the original Win32 compilation results. Do you like to compile the same program under mingw, but pay attention to if the mingw itself cannot compile this program in Cygwin, add -Mno-cygwin, is meaningless. I personally tend to use the Cygwin environment, how to think, very cool.
The development direction of MINGW and DJGPP is the primaryization of the platform, so it can directly produce native applications of each platform. Most people choose MINGW or DJGPP is to see this. The DEV C website is also available at the same time is the package download of integrated mingw. Djgpp I have not used it, but it is a 32-bit program under the 16-bit environment, interesting!
These purposes are to help you choose a branch that is your own.
Build your own strong development environment
If the wheel is the strongest dev C cygwin, everyone likes Mingw, then I will talk about this platform skill.
What we need is DEV C minimal package, then go to a Japanese friend's website http://www63.tok2.com/home/bitwalk/download.html#mingw
Download his MingW environment integrated installer, this looks like this, and all of all things are also relatively new!
First install the MINGW environment and then install DEV C , all installed the execution program path and the path included in DEV C . If you need some DEV C encapsulated bags, you can use the DEV C update to install it. Since MingW and Cygwin linkers are the same way of work, these packages can be used, Cygwin can also be used! If there is a difference, it is also on the header file. More advanced self-production development kits are in my diary, sometimes this advanced application needs you to know more clearly to the C / C language and the target development package, otherwise you have no play! I just want to say that the modern compiler is not a program, but consists of multiple program programs, so ... Hey, you know! ! ! Quote address http://blogbus.com/blogbus/blog/diary.php?diaryid=11204
