Recommended slickedit and slickedit configuration methods
Slickedit compilation and Configuration Methods
Preface:
Slickedit is a very good general ide tool for software development. Previously, tools such as Vc were too large and many wanted functions were not; third-party tools such as ultraedit and sourceinsight may not be satisfactory. Recently, slickedit is quite useful. I only encountered some questions When configuring the compilation, construction, and re-building environments. Here I will record the exploration process.
Some of the information in this document comes from the network. It is not listed because the author's name was not excerpted at the time.
Corrected font Problems
Other interface configurations can be completed in the menu, without listing the method, but some fonts seem to need to be modified in the program file, the method is as follows:
Use ultraeditto open vs.exe and vsapi in the 16-way format. find the "OEM fixed font" in the DLL file and change the "terminal" to "fixedsys" (the reason why fixedsys is used is because the number of words is the same, so that the file cannot run properly after modification, do not change the file length .)
Compilation stage Exploration
1. About vsbuild
Vsbuild.exe is a built-in construction tool of slickedit. I personally think it is similar to make after a trial. Its syntax is:
Vsbuild [workshop name] [project name] [-T target name] [other options]
Available options include:
-C <configuration Name> This is generally not used
-B <buffer Name> did not figure out how to use it
-D: No construction. Only dependency is displayed.
-V verbose mode
-Quiet does not generate interaction and other types of messages
-Nodep does not process dependencies between projects.
-After beep is built, ring the horn.
-Time: displays the time consumed by the construction.
-WC has not figured out how to use it.
-Execute <command> this option must be at the end. If the target is successfully generated, run this command.
-Execastarget <command> should also be at the end
Note:
The workspace name actually points to the XXX. vpw file. This file is automatically generated after the workspace is created using slickedit. The project name actually points to the XXX. vpj file, which is also automatically generated.
If you use ultraedit to open the vpw and vpj files, the first line is
<! Doctype workspace System "http://www.slickedit.com/dtd/vse/10.0/vpw.dtd">
It reminds me of XML, so open the vpw. DTD file in the above path to clearly see the available vpw tags and the corresponding attribute values, and can roughly guess their meaning. Similarly, you can view the vpj. DTD file to understand the available vpj tags and the corresponding attribute values.
But in fact, no modifications were made to the two files during the configuration process, but some modifications were made for testing. For example, the exec Mark in target can be set to multiple, but only the first one will take effect. Write this section to let yourself remember this process.
2. configuration method
Preface:
After multiple tests, the best method I can find is to use makefile to add environment scripts.
Configuration process:
Take the VC project as an example. Because I am working on a Gina project, I need to use the VC environment, but it is not easy to write directly with VC (except for the interface ), because I cannot view the header file of the function to be used before compiling the project, but if I can compile it, it means that I already know which header file should be included, slickedit provides strong support in this respect, and basically all functions required by the development can be well satisfied.
I installed Windows 2003 ifs DDK instead of Vc in my system to develop a file filter driver and install Windows 2003 SP1 SDK for Gina, finally, an slickedit is installed. This document takes the three environments as an example to describe how to configure the slickedit development environment.
N create a project first and write a makefile for building (that is, build ).
N to be able to use the C environment, write a script file sdkenv. CMD with the following content:
Rem Part 1: Set the environment variables shared by various platforms
Rem suppose your SDK is installed in D:/program files/Microsoft platform SDK
Rem if you install the SDK in another path, modify the environment variable value accordingly.
Set mssdk = D:/program files/Microsoft platform SDK
Set bkofice = % mssdk %/
Rem basemake settings are actually set to use sources for compilation.
Set basemake = % mssdk %/include/bkoffice. Mak
Set inetsdk = % mssdk %
Set mstools = % mssdk %
Rem Part 2 set debugging-related environment variables
Rem specifies the/debug (= 0) mode or/retail (= 1) mode.
Set nodebug = 1
Rem Part 3 sets development-related environment variables
Rem ddkhome should point to your DDK installation directory
Set ddkhome = D:/winddk/3790
Set Path = % mssdk %/bin; % mssdk %/bin/winnt; % ddkhome %/bin/x86; % PATH %
Set Lib = % mssdk %/LIB; % lib %
Set mssdkinclude = % mssdk %/include
Set include = % mssdkinclude %; % mssdkinclude %/CRT; % mssdkinclude %/GL;
Set include = % include %; % mssdkinclude %/mfc;
Rem Part 4 set platform-related environment variables
Set CPU = i386
Set targetos = winnt
Set appv ER = 5.02
Rem Part 5 other settings that suit your habits
Rem because I am used to using make instead of nmake of VC (it is quite uncomfortable to add n more)
Doskey make = nmake & #36 ;*
N configure slickedit,
1) Create the project you need first
2) write the makefile of the project. (If you do not use makefile to compile the project, find the relevant materials and learn)
3) Open the "project" à "Project Properties" menu and click the Tools tab.
4) Select compile for configuration. In the command line edit box below, enter:
Sdkenv. CMD & nmake
Note that make cannot be used, even if doskey make = nmake & #36; * is used. Do not add double quotation marks to any command, slickedit seems to directly import this line of command to a cmd thread for running, so there is no quote. You can open a cmd window and run copy and copy to know the difference between the two, double quotation marks cannot be used.
Sometimes our project and the vpw file are in different directories. In this case, you need to modify the above command:
Sdkenv. CMD & CD <directory of your program file> & nmake
5) Now configure the build tool. In its command line editing box, enter:
"Xxx/XXX/vsbuile.exe" % w % R-T "compile"
Xxx/XXX/vsbuile.exe.exe to the absolute path of vsbuild.exe.
Note that slickedit processes build and compile in a different way. slickedit may pre-process build, so double quotation marks can be used here, note that slickedit transfers the string in double quotation marks as a "single" command to the console without analyzing the string in double quotation marks. For example:
"Xxx/XXX/vsbuile.exe" % w % R-T "compile"
"Xxx/XXX/vsbuile.exe" % W "" % R ""-T "" compile"
But cannot be written
"Xxx/XXX/vsbuile.exe % W" "% R-T compile"
"Xxx/XXX/vsbuile.exe" "% w % R"-T compile"
.
6) Now configure the rebuild tool. In its command line editing box, enter:
Sdkenv. CMD & nmake Clean & "xxx/XXX/vsbuile.exe" % w % R-T "compile"
According to the rules mentioned above, you can also write
"Sdkenv. CMD" & nmake "clean" & "xxx/XXX/vsbuile.exe" % w % R-T "compile"
.
But cannot be written
Sdkenv. CMD & "nmake clean" & "xxx/XXX/vsbuile.exe" % w % R-T "compile"
.
7) work. Now you can build with Ctrl + M and compile with Shift + F10. The functions provided by slickedit allow you to fully enjoy development.
Configuration instructions:
L many symbols (for example, %) use full-width symbols. Therefore, a running error occurs when you copy them directly to the file.
L The configuration here only meets my development needs. If your environment has other requirements, you should modify the Command Script on your own.
L The value of the environment variable appver is related to the target platform in which the program will run in the future:
Windows 2000 ----- 5.00
Windows XP 32-bit ----- 5.01
Windows XP 64-bit/Windows 2003-----5.02
L The CPU value of the environment variable is related to the target platform where the program will run in the future:
Intel 64-bit ---- IA64
AMD 64-bit ---- amd64
L if it is a 64-bit platform, you should set the environmental variable msvcver
Msvcver = win64
L The above settings are relatively complete VC environment settings. In fact, in many cases, you only need to set the third part.
3. Other configuration methods
If you have installed VC (vc6 is vc6; vc7.0 is Visual Studio 2002; vc7.1 is Visual Studio 2003; vc8.0 is Visual Studio 2005), you can use other configuration methods.
You can use the msdev.exe tool to build vc6. (if you cannot find it, search for it on the local machine)
In vc7, devenv.exe can be used for construction.
The syntax of these two tools can be written into the corresponding tool configuration of slickedit, which can also complete the compile and build work. Even slickedit has built-in support for Visual Studio 2002 (which can be opened directly. sln files), but earlier and later versions are not supported. To find the devenv.exe tool J of vcss, you must install Visual Studio in the system.
For how to use msdev.exeand devenv.exe, enter
Msdev /? Or devenv /? For more information, see the usage of vsbuild.
