This article is reproduced from: http://blog.9cbs.net/visioncat/archive/2004/08/04/65431.aspx
DEV-CPP / MINGW32 Environment Introduction (2)
Review:
Above ("DEV-CPP / MINGW32 Environment Introduction (1)") We know how to install and use DEV-CPP. Also, some use of some usage and some procedures for the MINGW32 and how to use the procedure are known. Learn some of the basic operations. Such as new projects, compile projects, etc. This time, we will continue the last content.
Chapter 3 Installing and Developing Package for Your DEV-CPP
For many programmers, let a set of developments and a combination of my favorite IDE is the most prosperous. Natural me too. The last time we learned how to create a new project in DEV-CPP. However, in the uncomfortable, she seems to only create some simple programs. For example, a console program, dynamic connection library, static connection library, etc. It seems that it is difficult to complete a complex work. Of course, the C / C language is a development language that encourages code reuse. We can set up each new project to use the development kits you like and habit. However, this may be too cumbersome. Moreover, the documentation that is installed and compiled for these developments is too trouble. Therefore, DEV-CPP provides the concept of a package for developers. There is a package management system in the DEV-CPP. With this system, you can easily install various development kits. With this, your dev will become more and more smooth. It is like a title "Sharp Tool" in "Month" in "Month". Let's take a step by step to learn how to install the development kit. First, we must have a development package that has been done. We can get from the official website of DEV-CPP. Here is the address of the development package download page at www.bloodshed.net/dev/packages/index.html you can find a lot of you familiar with. Of course, if you don't have tools with tools you like. If you think these tools are too ancient, or not enough. There is some address of the mirror site below the page. Typically, these mirrored content is much larger than the main station. So you can get these packages from many ways. Now we will download one as a drill. If you don't recommend it, we download a Fast Light Toolkit. Of course, you can also download other packages. I just as a explanation here. After the download is complete, we will get a file with a suffix * .devpak. This is the development package file. The use of this file is the same as the installation file we usually used. Different, the installation file will modify the registry and put the installation information. If the system is reinstalled, you will need to reset the program. This installation file does not write the installation information to the registry. Also, as long as the directory of the installer is not deleted. When you install it next time, you will not be installed again. Unless used MingW32 new or old cannot be supported. Now, we save this file well. Next, you can introduce the Package Manager this program you can start with two ways. One is to click the tool menu in the DEV, select the final package manager. Another method is to run Packman.exe directly in the installation directory. You will see an interface below after running.
If you are running, you have not seen the toolbar on the left or the toolbar above. You can choose all of the options in the View menu. Here is some ways to operate. Where the Install button is used to install the development package. The Verify button is used to check the integrity of the development package. The REMOVE button is used to delete the development package. The intermediate blank part of this interface is to display the development package icon, the toolbar on the left is used to display the development package information. This includes information such as the name, version number, introduction, and provided site. The top toolbar is used for easy user operation. There are basically menu. There is a toolbar. Therefore, the ordinary work tool bar can be completed.
Ok, here. Let's say it back. The so-called speech is transmitted, it is probably sent to this manner. (How to suddenly think of Mr. Lu Xun's "A Q Zheng Chuan"? It's strange.) We introduce the method of installing the package. There are two ways to install the toolkit, of course, it is the two kinds I often used. As for any other method. Naturally there is. It's just that I personally still like these two. If any of the proliferation methods are naturally available. As long as you can use it smoothly, what method can be understood. The so-called road path is Rome. Sometimes, we don't have to worry too much, we want the results. The first method is that we usually use the installer. Double-click Toolkit directly. Package Manager will be very enthusiastic to help you complete the task. Then, you will be more prompting step by step. This method is indeed very good. Just feel that it is not professional enough. If you are seen, it will be considered by others. So, I will introduce the second installation method for everyone. First run the package manager first, then click the Install button. She will prompt you to tell her the kit. As long as you choose the toolkit, click OK. The rest is the same as the first method. This method looks more old birds. But too much trouble. Is not it? So, is we going to choose a rookie and old bird? Of course not. My personal opinion is that I usually use the first method. Some people ask for it, use the second method. Ok, after installing. We will see more icons in the package manager. This is the toolkit you just installed. If you feel uncomfortable, you can choose her and press Remove. Below you may ask me, I am installed. How to use it? Ask good, it is worthy of praise. This problem ... Of course it is very simple. If you can't even answer this, how can I say here, where are you listening there? (Hey, I have to say that I will go home early ...) For different development kits, the method used is different. If it is an IDE itself a development package. So, the IDE will be called at runtime when using the IDE. You don't have to worry. You know, a person is worried too much about many wrinkles and a lot of brain cells. Some development tools can be seen in the new project, as for where to see specific packages. Next I still take Fast Light Toolkit as an example. To use the method of use. Fast Light Toolkit is a GUI development package. (I think you should know what is Gui, the simple little is Graphical User Interface. It is complicated, it is the user interface). We now start to create a new project, this has been introduced above. However, this time I changed some changes when I determined the project. This time, we have selected the GUI tab in the dialog box that appears after clicking New Project. Then select FLTK. Because FLTK is used for C . Therefore, we can only use C here (how to have a hard feeling). The next thing is the same as the last time we say. DEV automatically generates a file of main.cpp. There are some basic code inside. After saving, compile, run. You can see a Windows interface you admire. (Ah, finally see you, window) I think, so smart, you should give it an anti-three, know how other toolkits can be used. The so-called, Master leads to the door and practice itself. I can't get in place in one step. Finally, I want to ask you to pay attention. Before installing the package, you must first see the instructions for the relevant package. Because some packages are dependent, you must install her after installing a package. This is like it is to know that some results cannot be the same as the order of operation. For example, you must have a wife first, then there is a son.
(Unless special circumstances) Chapter IV Project Import and Export
The four numbers are always less beautiful. In China, it seems to be like this. Since we can't skip four, it is directly until five (because others will think that it is not a life-throwing chapter, I feel unfortunately), I will introduce some unrelated classes. Even if you don't get groom, it will not affect us. For those developed with VC. There are many projects to develop under DEV and re-setup and write, they will feel a headache. So, DEV added a function of converting VC6.0's engineering files into DEV project files. (This is a good turn, the next time it changes it into a winding order) is a good news. First, we must have a VC6.0 engineering test. There is no relationship, see if long-term knowledge is also good. Anyway, this chapter is not a matter of itching. Then we started importing. Select file, import, import Visual C Project. After clicking, a dialog will appear. Select the path to * .dsp in the first option (you can fill in, as long as you can write the full path). After the selection is complete. The dialog box will appear some properties of the project. You can choose when you choose. For example, the content in the second box is to ask you to import that generation configuration. DEBUG or RELEASE is still something else. In the third box, what is you want to put the devil project file. (Of course, on your own computer, where is it? Is it possible to bring the courage to Mars?) It can be sure it will be ok. After waiting for a period of time (specific length, you have to see how your program is in size, if you write Linux kernel, then you have to wait for a longer time. If any, if any Now open the DEV project to see. How, everything is normal. Is it very excited? Perhaps someone wants to ask, why is this important feature? In fact, it is more likely to use. The imported code can be successfully compiled, as you are lucky to be prepared to buy a six-color. Because, until now I haven't introduced a project that can be successfully compiled. (If you can, remember to tell me, so let me know the legendary imported project). The next function is exported. This feature is of course not like the last function. However, the function will not have too much use for general developers. Don't think that this export and the above import are relative. That is to export the DEV project into VC6.0 project. This export is that the C / C file project exports into a web form. Or writing on the form. If you are using this project to do tutorials, it is a very good feature. However, developers still write code greater than writing a tutorial (it seems that I am an undressed developer). So, I think this function is somewhat unrelated. Here are the method of use. Select a file, there will be three options after exporting. To HTML, to RTF and Project to HTML. The first and second is exported for a single file. The third is to export throughout the project. (All code) first, the second export file I don't have to introduce it. Anyway, there is one file. I specifically introduced the third generated file. The third generation of * .html, * content is determined by you. And a folder of a list of Code. The program code that is converted to the HTML file is included. Of course, these code are colored prompts, very good. In this way, the so-called export project is actually converting the entire project document into a function of the website tree structure. Therefore, this feature is used to illustrate the code is very good. I introduced it here, introduced some features that itching. I think you may have a probably understanding of DEV-CPP.
If you want to know more about importing and export features. It can be proposed. Let's solve it together. Textual sound:
The article is temporarily introduced here, and will continue to introduce. There will be one by one by one by more content for DEV-CPP / MINGW32. Stay tuned. I feel this article, it seems that there is no last time, and the writing style has also changed. If you like this style, I will use more in the future. If you don't like it, please ask you to like that style. I will be used as a reference. In addition, I hope that you will advise you. My motto: Whether it is a procedure or thinking, only through constant exchanges can be more perfect.
Studio software development group
Beidou Ringjun (Huang Yucui)
