Introduction to wince subproject

Author: arm-WinCE

 

Create a wince project in platform builder, and then you can see the "subprojects" item in the "Solution Explorer" window. It is mainly used to create some simple application projects in some wince projects. The project created here is finally compiled and packaged into NK. Bin. After wince is started, you can find the corresponding execution file under the Windows directory.

Create or add subproejct. Right-click subprojects and the following window is displayed:

 

 

Select Add new subproject ..." Later, follow the wizard step by step. Currently, Subprojects support the following projects:

Wce Application

Wce console application

Wce dynamic-Link Library

Wce static library

Wce tux dynamic-Link Library

 

I will not describe the meaning of each project here. I believe everyone who develops the application will understand it. After the project is created, you can program it. A common problem is to link the required library file. You can right-click the project name and select "properties ", in the displayed dialog box, select "Link" and add the library to be linked in "additional libraries,

For convenience, I like to directly copy the required library files to the directory of the project, and then directly add a library file name here, without entering a long path. In "additional libraries", you can add multiple libraries, each of which is linked by a space. For example:

$ (_ Projectroot)/cesysgen/SDK/lib/$ (_ cpuindpath)/coredll. Lib ws2.lib mgprint. Lib

 

Besides linking the default coredll. Lib library, ws2.lib and mgprint. Lib libraries are added. Next, you can call the function by including the corresponding header file in the project.

 

In subprojects, we can create multiple projects and set the project compilation sequence. Right-click "subprojects" and select "set subproject build order…" in the displayed dialog box ...",

 

I recently wrote a simple subprojects, mainly for debugging, because it is a pure application.