Use slickedit to edit and compile the IAR project.

Slickedit is a fully functional editor. Note that he has an editor, but he has a vsbuild.exe program.

The biggest feature of this program is that it can track the content of the CMD window to achieve error targeting.

For example. If we use an configured mingw environment to compile a makefile, we can write an Env. the bat script runs in cmd, registers the environment to the system environment, and then enters the project directory on the CMD interface. A make command can be compiled. However, when an error occurs, you have to find one row. Is this convenient?

But if we create a slickedit project and pull all the files in it, open its build interface, repeat the above steps, and then click the error or warning .. Is it automatic jump ?? That's how I used it.

This is a special feature of slickedit ..

The next step is IAR. IAR is an embedded compiler with high compilation efficiency, but its editing function is also very criticized.

Therefore, we often want to use an external editor to edit the file and compile it in IAR .. Of course, IAR can also call external editors, but the efficiency and error locating functions are not the same. After you compile the editor, you still need to save it, And then directly switch to IAR to continue compilation. So I want to use the vsbuild function of slickedit to compile and edit IAR .. Of course, it also includes its own jump function.

First, the computer may need to install the IAR compiler in advance, and then configure an environment variable for the IAR installation path in the environment variable. I set it to iar_path, and the name does not matter, then install slickeidt, Which is 16.0 of the latest version.

Click project-> New. Under the displayed project type box, there is a customize... button to create a new project. We just need to create a new project category and configure the tool.

In the Mize project types pop-up window, click New ..., enter the name by yourself. It is important to select grenal C \ c ++ for the language in it. My version is not complete, but there is an other C \ c ++, so I chose this one. Go to the tool configuration page and click the toolsx configuration page. There are several configuration options. Click build. This is the compilation tool. Its function is to automatically compile the tool when you save it. Therefore, the command to be filled in is equivalent to make, and rebuild is compiled again, so the function is equivalent to build.

The next step is to start the configuration tool. At first, I just wanted to get started with  and xlink. The two programs compile, but the discoverer two commands can be used in this way, because both  and xlink require a lot of file names as variables .. is fine, but Link wants all file names as variables. I cannot achieve this at all .. So I had to do it, but recently I found that slickeidt can compile IAR in a foreign official slickedit forum. I suddenly realized that iarbuild.exe was a key program. Then I flipped through the IAR user manual and finally dug out the tool.

Iarbuild.exe is actually an EWP tool for directly compiling IAR. To use this command, you must have created an iar ewp project and included all the files.

The command format is iarbuild project. EWP [-clean |-build |-make] <configuration> [-log errors | warnings | info | all].

Project. EWP is the project name.

-Clean indicates the compilation result of the project,-build indicates all compilation, and-make indicates the compilation modification.

<Configuration> is the configuration of the selected project, such as debug and release. We usually use DEBUG when creating a project, so debug is used here.

The last level is a display message level. Errors. Warnings, info. All, and errors show only errors, warnnings show only warnings, info show final information, and all show all information.

Obviously, IAR errors are divided into four levels. Slick has only two error levels, so let's take the following command.

% (Iar_path) \ iarbuild % rn. EWP-build debug-log Info (% rn indicates the current project name)

When compiled as a command, you will find that during compilation, vsbuild prompts that you do not know the-log info behind it...

How can this problem be solved .. In fact, it is very simple, that is ........
..

If the last-log is not added, the default setting is used by default. And no error is reported.

Therefore, based on the above content, we can configure three tools, but we generally use make and build ..

% (Iar_path) \ iarbuild % rn. EWP-make debug

% (Iar_path) \ iarbuild % rn. EWP-build debug

% (Iar_path) \ iarbuild % rn. EWP-clean debug

Save and create a new slick project in the IAR project directory, and pull all the files to slickeit. Note that the project name must be the same. Required. Otherwise, how does it know the project you want to compile .. Another point is... The slick project cannot have a Chinese path. Otherwise, the system will keep prompting you to save the file... This is also a headache I encountered.

Send an image for specific configuration ..

It is worth noting that this is a permanent task. After setting the type, you do not need to reconfigure it next time. You only need to select the project type .. Okay, you can try to compile it, directly build it, or save the file ..

Finally, you must note that if you want to extend the variable search function of slick to the IAR library... You need to include the IAR path in the include of the set directories of the project type .. But because different IAR files have different header files, it is better to add them separately... = Do not add it to the project type. After all, this is universal ..

--And... A lot of knowledge comes from the Internet and is not very important... But... Absolutely original. Please indicate the source of the post .... Refuse to steal ....

Http://blog.csdn.net/xuzhenglim/article/details/6938132