Dev-CPP/mingw32 Environment Introduction (2)

Dev-CPP/mingw32 Environment Introduction (2)

Review above:

The above (Dev-CPP/mingw32 Environment Introduction (1) shows how to install and use Dev-CPP. In addition, I learned some usage of mingw32 and some introduction and usage of related programs. I learned some basic operations. Such as new Project Creation and project compilation. This time, we will continue with the last content.

Chapter 3 install the development kit for your Dev-CPP

For many programmers, it is a pleasure to combine a favorite development kit with a favorite IDE. Naturally, me too. The last time we learned how to create a project in Dev-CPP. However, what is lacking in the US is that she only seems to be able to create some simple programs. For example, console programs, dynamic connection libraries, and static connection libraries. It seems difficult to complete a complex task. Of course, the C/C ++ language is a development language that encourages code reuse. We can set each new project to use the development kit we like and are used. However, this may be too cumbersome. Besides, it is too troublesome to install and compile these development kit files. Therefore, Dev-CPP provides the Package concept for developers.
There is a package management system in Dev-CPP. With this system, you can easily install various development kits. With this, your Dev will get better and better. That's just like the title "sharp tool" of an article in man-month. Next we will learn how to install the SDK step by step.
First, we must have a ready development kit. We can get it from Dev-CPP's official website. Here is the address of the download page of the Development Kit www.bloodshed.net/dev/packages/index.html on which you can find many tools you are familiar. Of course, there are no tools similar to your favorite tools. If you think these tools are too old or not enough. There are some image site addresses at the bottom of the page. Generally, these images are much richer than the main site. Therefore, you can get these packages in many ways. Now we can download one as a drill. If not, download a fast light toolkit. You can also download other packages. I am here to explain it.
After the download is complete, we will get a file with the suffix *. devpak. This is the Development Kit file. This file is used in the same way as the installation file we usually use. The difference is that the installation file will modify the registry and add the installation information. If the system is re-installed, you need to re-install the program. The installation file does not write the installation information into the registry. In addition, as long as the installation program directory is not deleted. Next time you install it, you are not allowed to install it again. It is not supported unless the mingw32 is too old or too old. Now, we can save the file.
Next, let's talk about the Package Manager program in two ways. One is to click the tool menu in Dev and select the Package Manager of the last item. Another method is to directly run packman.exe in the installation directory. After running, you will see the following interface.

If you do not see the toolbar on the left or the toolbar above after running. You can select all the options in the View menu. The following describes some operations. The Install button is used to install the SDK. The Verify button is used to check the integrity of the Development Kit. The Remove button is used to delete the SDK. The blank part in the interface shows the development kit icon, and the left-side toolbar is used to display the Development Kit information. The information includes the name, version number, description, and provided site of the Development Kit. The toolbar above is convenient for users. Basically, there are some in the menu. The tool bar is available. Therefore, the normal work toolbar can be completed.

Okay, here. Let's talk about it again. This is probably a handy example. (Why did we suddenly think of Mr. Lu Xun's Q Zheng Chuan? It's strange .) We will introduce the installation package method.
There are two ways to install the toolkit, of course, I usually use two methods. Is there any other method. Naturally. I personally prefer these two types. If anyone has any strange method, you can use it. As long as it can be used smoothly, any method can be understood. The so-called routes allow Rome. Sometimes, we don't have to worry too much about the method. What we want is the result.
The first method is like using the installer. Double-click the toolkit. The package manager will jump out to help you complete the task. Then, you will be prompted to step by step. This method is really good. I just thought it was not professional enough. If you see it, it will be considered a cainiao by others. Therefore, I will introduce the second installation method here. First, run Package Manager and then click Install. She will prompt you to tell her where the toolkit is located. Select the Toolkit and click OK. The rest is the same as the first method. This method looks a little old. But it is too troublesome. No? So should we make a choice between cainiao and laruence? Of course not. My personal opinion is that the first method is usually used. If someone asks for something, use the second method.
Okay. After installation. We will see an additional icon in Package Manager. This is the Toolkit you just installed. If you feel uncomfortable, select her and then press remove.
Next you may ask me, I have installed it. How to use it? I am very grateful for the question. This question ...... Of course it is very simple. If I cannot answer this question, how can I say it here? Where are you listening? (Ah, I wanted to go home and go to bed early ......) Different sdks are used in different ways. If it is an IDE development kit. Then, when you use the IDE, the IDE will call it at runtime. You don't have to worry about it. You know, if you worry too much, there will be a lot of wrinkles and a lot of brain cells. Some development tools can be seen in the new project, where the specific depends on the specific package.
Next I will take the fast light Toolkit as an example. To describe how to use the package. Fast Light toolkit is a GUI development kit. (I think you should know what a GUI is, simply put, graphical user interface. A little more complicated, that is, the user interface. Now we start to create a new project, which has been introduced in the previous article. However, this time the project was confirmed to be somewhat changed. This time, in the dialog box that appears after you click Create Project, select the GUI tab. Then select fltk. Because fltk is used in C ++. Therefore, here we can only use C ++, and C is not optional (how can we feel hard ). Everything is the same as what we said last time. Dev automatically generates a main. cpp file. There are some basic code. Save and compile and run. You can see an old Windows interface that you admire. (Ah, I finally saw you, the window) I think, you should be wise to know how to use other toolkit. The so-called, Master leads the door, practice depends on oneself. I can't do it in one step.
Finally, I would like to pay attention to it. Before installing the installation package, check the description of the package. Some packages are dependent and must be installed after a package is installed. This is like knowing that sometimes the same results cannot reverse the operation order. For example, you must have a wife before you have a son. (Unless otherwise specified)

Chapter 4 Import and Export of projects

The fourth digit is always unlucky. This is the case in China, and it seems like this in foreign countries. Since we can't skip step 4 and go straight to Step 5 (because of this, others will think that they have missed a chapter and feel sorry for the rest of their lives), I will introduce some irrelevant things in this chapter. Even unlucky, it won't affect our development.
For those who are used to VC development. There are many projects that need to be re-configured and written under Dev, which can be a headache. Therefore, Dev adds a function in it to convert the project file of vc6.0 into the project file of Dev. (This sentence is easy to use. I will change it to a tongue twister next time.) That's good news.
First, we must have a vc6.0 project for testing. It doesn't matter if you don't know it. This chapter is about the content that is irrelevant. Next, we started importing. Select a file, import it, and import the Visual C ++ project. A dialog box is displayed. Select *. DSP path in the first option (you can also enter it as long as you can write the complete path ). After selection. The dialog box displays some properties related to the project. You only need to select. For example, the content in the second box is to ask you to import the generated configuration. Debug, release, or something else. In the third box, you are asked where to put the dev project file. (Of course, it's on your own computer. Where else? Isn't it possible to bring the brave guy to Mars ?) After selecting all, you can press OK. Wait for a while (the length depends on the size of your program, such as Linux kernel compiled by VC. It takes a long time. If yes ). Open the dev project now. How are you doing? Everything is normal. Are you very excited? Some may ask why such an important feature is irrelevant? In fact, it is even more useful to me. The imported code can be compiled successfully. You are lucky to be ready to buy the Six-color combination. Because, until now, I have not imported a project that can be compiled successfully. (If you can, remember to tell me, so that I can see the legendary import project ).
The next function is export. This feature is certainly not the same as the previous one. However, features are not very useful for general developers. Do not assume that this export is relative to the above import. Is to export the dev project to the vc6.0 project. This export refers to exporting the C/C ++ file project to a webpage. Or in the form of a wordpad. If you are using this project as a tutorial, it is indeed a very good function. However, developers should write code more than write tutorials (as if I am a nonprofessional Developer ). Therefore, I think this feature is irrelevant. The following describes how to use it.
Select a file. After export, there are three options. To HTML, to RTF, And to HTML. The first and second files are exported to a single file. The third is to export the entire project. (That is, all the code) First, I do not need to introduce the second exported file. That's a file. I will introduce the third generated file in detail. The third generates a *. html, * content is determined by you. And a folder named code. It contains the program code converted into an HTML file. Of course, these codes are color-coded and very good. In this case, the so-called export project is actually to convert the entire project file into a function similar to the website tree structure. Therefore, this function is used to demonstrate that the code is very good.
Here we will introduce some irrelevant functions. I think you may have a rough understanding of Dev-CPP. If you want to know more about the import and export functions. It can be proposed. Let's work together.

 

VOICEOVER:

The article will be introduced here for the time being and will be further introduced later. More information about Dev-CPP/mingw32 will be displayed in the future. Coming soon.
I think this article is not as golden as it was last time, and the writing style has changed. If you like this style, I will use it more in the future. If you do not like it, please say that you like it. I will serve as a reference.
In addition, I hope you will give me more advice. My motto: Programs and ideas can be improved only through continuous communication.

 

Studio software development team

Dipper (Huang yaokui)