I. Building a QT embedded environment
A) first download QT embedded development kit qt-embedded-wince-opensource-src-4.4.0.zip
B) then, download vs2005.
C) Finally, download an Embedded Development SDK, such as Windows Mobile 5.0 Pocket pc sdk, which can be downloaded on Microsoft's official website!
D) Another software is Microsoft activesync4.5 Simplified Chinese version.
------------------------------------------ An ---- installs ----------------------------------
E) install vs2005 first, which is very simple. Follow the Wizard to select "smart device development" for custom installation ".
F) The installation of Microsoft activesync4.5 is "straightforward ". I will not talk more here!
G) then, install Windows Mobile or other versions of the SDK, you can use the custom SDK! Simple
H) The trouble is the installation of QT-embedded-wince. Follow these steps: ①. decompress the folder and place it in a path without spaces. For example, F: \ pengu.pdf \ qt_wince and qt_wince are the folder. Then set the environment variable: right-click "my computer"-> "properties"-> click the "advanced" tab-> "environment variable" option-> Add path "F: \ pengu.pdf \ qt_wince \ bin ". OK! ② Compile the foreplay. First, configure the compilation options, run the vs2005 command line, enter the decompressed folder, and then execute the following: configure-platform win32-msvc2005-The xplatform wince50standard-armv4i-msvc2005 can choose other embedded xplatfrom based on your own board and phone configuration. This process may take 10 minutes. After the execution, set the temporary environment variable in vs2005 again and use it during compilation as follows:
Set include = D: \ Program Files \ Microsoft Visual Studio 8 \ Vc \ ce \ include; D: \ Program Files \ Windows CE tools \ wce500 \ Windows Mobile 5.0 Pocket pc sdk \ include \ armv4i
Set Lib = D: \ Program Files \ Microsoft Visual Studio 8 \ Vc \ ce \ Lib \ armv4i; D: \ Program Files \ Windows CE tools \ wce500 \ Windows Mobile 5.0 Pocket pc sdk \ Lib \ armv4i
Set Path = D: \ Program Files \ Microsoft Visual Studio 8 \ Vc \ ce \ bin \ x86_arm; % PATH %
Here, I hope to "Remove" the above directory based on my software installation. After the settings are complete, run nmake. After two or three hours, you can enjoy your journey.
Finally, run nmake to complete the installation! My QT-wince is installed on F: \ pengu.pdf \ qt_wince
2. Compile the QT-wince Program
Command Line Method (IDE is not required ):
First, use the vs2005 command line to enter the program directory to be compiled (this directory is preferably under the installation directory F: \ pengu.pdf \ qt_wince), and execute <F: \ pengu.pdf \ qt_wince> bin \ qmake.exe-project-O example. in pro, install QT path to your QT-wince installation directory. At this time, the example. Pro file can be generated.
Then, when the makefile is generated: Enter the following command in the vs2005 command line:
F: \ pengu.pdf \ qt_wince \ bin \ qmake-spec .. \ mkspecs \ wince50standard-armv4i-msvc2005-Win32-O makefile example. pro at this time, congratulations, MAKEFILE file has been generated.
Finally, nmake is used to compile and link the program. Run the environment variables (three sets) during installation in the current vs2005 command line again. Otherwise, the following error occurs:
CL: command line warning d9002: ignore unknown option "-qrarch4t"
CL: command line warning d9002: ignore unknown option "-qrinterwork-return"
Main. cpp
Mainwindow. cpp
F: \ pengu.pdf \ qt_wince \ include \ qtgui \ http://www.cnblogs.com/src/gui/widgets/qmenu.h (144): Error C2
146: syntax error: ";" missing (before the identifier "wcemenu)
F: \ pengu.pdf \ qt_wince \ include \ qtgui \ http://www.cnblogs.com/src/gui/widgets/qmenu.h (144): Error C4
430: The type specifier is missing-it is assumed to be Int. Note: C ++ does not support default int
F: \ pengu.pdf \ qt_wince \ include \ qtgui \ http://www.cnblogs.com/src/gui/widgets/qmenu.h (144): Error C4
430: The type specifier is missing-it is assumed to be Int. Note: C ++ does not support default int
F: \ pengu.pdf \ qt_wince \ include \ qtgui \ http://www.cnblogs.com/src/gui/widgets/qmenu.h (144): Warning
C4183: "wcemenu": The return type is missing. It is assumed that it is a member function that returns "int.
Then, execute nmake and watch the loss of Silver Line, it is gold (your EXE file.
Note: The following error message may be displayed during nmake execution:
Link/libpath: "F: \ pengu.pdf \ qt_wince \ Lib"/libpath: "F: \ pengu.pdf \ qt_wince \
Lib "/nologo/nodefalib Lib: oldnames. lib/debug/subsystem: WindowsCE, 5.00/Machin
E: thumb/out: Debug \ node.exe @ C: \ release E ~ 1 \ User \ locals ~ 1 \ temp \ nm6b3. tmp
TMP \ OBJ \ debug_shared \ main. OBJ: Fatal error lnk1112: module computer type "x 86" and target
Computer type "Thumb" Conflict
Nmake: Fatal error u1077: "D: \ Program Files \ Microsoft Visual Studio 8 \ Vc \ ce \ B
In \ x86_arm \ link. EXE "": return code "0x458"
I am helpless with this kind of error. If I don't execute nmake or directly execute nmake release, isn't this kind of error? This error may be because "F: \ pengu.pdf \ qt_wince \ bin" is set in "path" in "environment variable ". After I remove this variable, re-open the vs2005 command line (because you have to re-read the PATH variable ). Then follow the steps above and use nmake to execute it again. It is very smooth!
3. Deployment of the QT-wince Program (not packaged)
You can directly cp the *. EXE file developed above and the *. dll file it requires together to a directory. These DLL files generally include:
D: \ Program Files \ Microsoft Visual Studio 8 \ Vc \ ce \ dll \ armv4i \ msvcr80.dll
F: \ penguinx \ wince_vs2005 \ Lib \ qtcore4.dll
F: \ pengu4.\ wince_vs2005 \ Lib \ qtgui4.dll
For other projects, you can run CP.
If you want to deploy the program *. in the form of cab, in the above solution, click "file"> "new"> "project"> click "other", where there is a smart device deployment, I developed it on the lab machine and came back to write the note. So the specific operation is not very clear! ). After the Wizard is created, click "properties" in the newly created cab project and generate it. CP can be run on the board.
Note: All the CP is transmitted via USB using ActiveSync software. Of course, you can use other transmission means to finally use the board.
-Zm200-w34100-w34189-zm200-w34100-w34189-w34100-w34189
Note that if the wince version on the device is lower than the development version, the system displays "***, the Windows version to be updated" cloud.
/Subsystem: WindowsCE, 5.00/machine: thumb
/Subsystem: WindowsCE, 5.00/machine: thumb