Shulou(Shulou.com)06/02 Report--

What are the common skills of the VS2003 version? for this question, this article introduces in detail the corresponding analysis and solutions, hoping to help more partners who want to solve this problem to find a more simple and feasible way.

I use VS2005, and when I use these samples, basically most of the VS2003-based Asp.net projects cannot be loaded because a few files cannot be converted, which bothers me for a long time, and finally let me find a solution for the VS2003 version.

The following is mainly aimed at the establishment of the development environment of S60, so first of all, list the various versions of the S60 system. Because developers should choose their own version of SDK according to their needs.

1. Series60 * * version-Symbian OS 6.1

2. Series60 second Edition-Symbian OS 7.0s

3. Series60 second edition Pack 1-Symbian OS 7.0s

4. Series60 second edition Pack 2-Symbian OS 8.0a

5. Series60 second edition Pack 3-Symbian OS 8.1a

6. Series60 third Edition-Symbian OS 9.0

It is important to note that there are many kinds of integrated development environment [IDE] tools supported by Nokia's Symbian/Series60 development package. Some of the main IDE are listed below:

1 、 Microsoft Visual Studio 6 / Visaul C++ 6

2 、 Microsoft Visual Studio .NET [2003] / Visaul C++ 7

3 、 Borland C++ Builder 6

4 、 Borland C++ Builder X 1.0

5 、 Metrowerks CodeWarrior Studio for Symbian Personal/Professional 2.0/2.5

If you are using VC6 IDE, then the steps will be different from this article. You can refer to other tutorials online. More than 90% of the articles that teach Symbian environment settings online are based on VC6. If you use VS2003, but the SDK you use is different from the one used in this article, this article still applies, but it may change in some places.

If you have any questions to raise, let's discuss them together. This article does not talk about installing Nokia Developer Suite-Carbide.vs to cooperate with the import of VS2003 and the establishment of S60 project. This section will be explained in detail when the next article explains how to build and import a project. So you can not install the software for the time being. After you have set up the environment according to the instructions below, install this software to do further research. For details of this content, please refer to: introduction to Symbian OS Development (2): import and establishment of Symbian projects in VS2003 environment.

I used to use VC6 as IDE, and I am not very familiar with the development under VS2003. I am a beginner in Symbian development. What I write here are most SDK-based development documents, combined with some lessons from my own testing. To write it out, on the one hand, we can guide beginners like me to get started as soon as possible, on the other hand, we can also discuss and solve some empirical mistakes on this basis. Help newcomers avoid detours.

Detailed steps for establishing the development environment

I. system requirements

The document contains some requirements for your PC, which is to make sure your computer can run VS2003 and SDK. There's usually nothing wrong with it. The system requires more than Win2000 SP3, more than WinXP SP1, any kind of Win2003.

II. Software installation

Note: before installing SDK, make sure that the following 3 items are installed correctly. When installing the software, you must make sure that the account you use is your PC administrator account, otherwise some environment variables may not be set correctly. SDK and IDE are to be installed in the same partition on the computer. The installation path of SDK cannot contain spaces. The software that needs to be installed and its steps are described in detail below:

1. ActivePerl must be installed before installing SDk (official documentation requires that Perl 5.6.1 build 531 be installed, and that there may be problems installing other versions. I tested using ActivePerl-5.6.1.638-MSWin32-x86 myself and ran well). The software can be downloaded from the official website: http://www.activestate.com/Products/ActivePerl/

2. Install JAVA Run-Time1.4.1_02 or new version, and download the address http://java.sun.com/downloads/index.html..

Description: you don't actually need to use JAVA Run-Time1 when compiling programs using the command line. But I'll mention later that if you want to use ApplicationWizard, a powerful tool of SDK, you must install this component, and if you want to use tools such as Sisar, JRE is also necessary. Please install it here first.

3. Install IDE, as mentioned earlier, install Microsoft Visual Studio .NET 2003

4. To install SDK, note that the installation path of SDK mentioned above cannot contain spaces. And install it in the same partition as IDE, so you can avoid some trouble. Download address: http://www.forum.nokia.com/main/0,6566,034-4,00.html

5. Install Nokia Developer Suite-Carbide.vs. This is the equivalent of a plug-in for VS2003 to help you import or build S60 projects so that you can write code in VS2003. (this article does not explain how to use it for the time being. You can install it first or install it later.)

Download address: http://www.forum.nokia.com/main/0,034-902,00.html

III. Check the environment variables of VS2003 version

Before version 2.0 of SDK [excluding 1.2For CW], you need to set an environment variable named EPOCROOT in the system variable environment, (what is the environment variable, how to set it, this goes to self-study), he should point to your SDK that contains the path of epoc32, there is no drive letter in front, and a "\" should be added at the back, which is usually added automatically after you install SDK. However, there is no need to set up [including 1.2 For CW] after 2.0. there is a SDK management tool called devices that provides similar functionality to simulate EPOCROOT environment variables for tools that need to use this variable. Think of devices as multiple Symbian SDK, not limited to S60. You have to switch tools. After you have installed 2.0SDK, type devices-help in command line mode to get help.

The version of SDK we use does not need to set too many environment variables. Here, you just need to add and modify the environment variables yourself, and add them to the system environment variable path:

{the installation path of VS2003}\ Microsoft Visual Studio .NET 2003\ Vc7\ bin; to ensure that the LINK.EXE used later is set correctly.

4. Compile and run "Helloworld"-check whether the development environment is set up correctly

After the above installation steps are completed, it is not done yet, so what you need to do is to check that your environment is set correctly. How to make sure that the development environment has been set up correctly? The way to confirm is to verify by compiling and running an example. It is important to point out that the following steps can be done in a command line tool in Windows or in the Visual Studio .NET 2003 Command prompt, a tool that comes with VS 2003. The advantage of operating in the command line tool of VS 2003 is that it can avoid errors caused by the incorrect setting of some environment variables, because it contains not only the contents of PATH variables in the system environment, but also some paths added during the installation of VC++.NET, including tools such as major compilation links. The downside is that if you just pass the verification here and fail the command-line interface that comes with WINDOWS, you will encounter some trouble later (such as using ApplicationWizard to build a project). So, if you don't use the Command prompt tool that comes with VC++.NET, you may not be able to continue because you can't find the corresponding compilation tool. If you are diligent, you can manually add the environment variables to the system PATH so that you can use the Command prompt tool in the Windows attachments menu, which may go smoothly later.

1. Open the command line interface of Windows (or the command line tool that comes with VC++.NET)

2. Set the SDK you just installed as the default devices. This can be set with the following command:

Devices-setdefault @ S60_2nd_FP2_SC:com.nokia.Series60

In fact, you will be prompted to set the default devices during the installation of SDK. The reason for doing this is that you probably have more than one SDK installed on your system, so which SDK to use as the current development tool needs to be set correctly. You can use the command line devices-default to see what the current default SDK is.

3. Find the directory where the Symbian project file is located

Now let's use the example that comes with SDK to verify that your environment is set up correctly. Note that after installing SDK, there are many examples in the Series60Ex folder in its installation directory, which we use helloworldbasic to verify. From the command line interface, use the cd command to enter the group directory of helloworldbasic:

Cd\ Series60Ex\ helloworldbasic\ group

The files bld.inf and helloworldbasic.mmp should be included in the group directory. A brief description of these two files is as follows:

HelloWorld.mmp: a project definition file that describes the project information to be built and defines some resource files and application information files. It is an environment-neutral file that can use a variety of tools to process and generate make files for various target environments. You can view the file using a text editor. The information is still very concise, including the build target, build type, source path, library files, header files, and so on.

Bld.inf: a component description file that lists all the projects included in a component, and the VS2003 version includes some additional build instructions. You can also view the file using a text editor. For this example, only one project HelloWorld.mmp is included.

4. Enter bldmake bldfiles on the command line

This command processes the bld.inf files in the current directory, specifically performing the following process

(1) generate directory C:\ Symbian\ 8.0a\ S60_2nd_FP2_SC\ epoc32\ BUILD\ SYMBIAN\ 8.0A\ S60_2ND_FP2_SC\ SERIES60EX\ HELLOWORLDBASIC

(2) in this directory, generate a series of Make files for a variety of target environments. Such as VC7.MAKE,CW_IDE.MAKE and so on.

(3) generate an abld.bat file in the current directory, which will be used later. In the VS2003 version, you can view the contents of the file. But it is recommended that you do not change its content manually.

The Bldmake command also supports other command-line options, and you can type bldmake directly for a brief introduction and check the SDK documentation for more information.

5. Enter abld build wins on the command line

Bldmake processes the abld.bat file obtained from the bld.inf file, making the abld command available. Abld.bat controls all aspects of building a project. The syntax of the Abld command is very flexible, and it has a number of command-line options that are combined to cover a variety of build requirements.

Note: if you are prompted that a file mspdb71.dll is missing, you can solve it by doing the following: under the installation directory of Microsoft Visual Studio .NET 2003. You can find this file in the\ Common7\ IDE directory. Just copy him to\ Vc7\ bin. Remind again that the previous environment variable should be set, otherwise you will stop running because of the lack of link.exe.

6. Enter: epoc on the command line

Then the simulator will appear. If your environment is set up correctly, there will be the helloworld you just compiled in the simulator. Its name on the simulator is "HW".

Check whether SDK and IDE are compatible

1. Repeat the above 1mi 4

2. Type: makmake helloworldbasic vc7 on the command line, and some files will be generated under the group folder. The VS2003 version contains the project file HELLOWORLDBASIC.sln of VS2003.

3. Open VS2003, select "Open solution (Open Solution)", open HELLOWORLDBASIC.sln, then compile and run, and you will get the effect in step 6 of part 4. (you may need to select the program epoc.exe at run time)

The answers to the questions about the common skills of the VS2003 version are shared here. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel to learn more about it.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.