]>
Commit | Line | Data |
---|---|---|
1 | ||
2 | ================================================= | |
3 | Welcome to wxWidgets/CE | |
4 | ================================================= | |
5 | ||
6 | You have downloaded the Windows CE port of the wxWidgets GUI library. | |
7 | This runs on Pocket PC 2002/2003, Smartphone 2002/2003, | |
8 | Windows CE .NET 4.x, and Windows Mobile 5. | |
9 | ||
10 | More information about the wxWidgets project as a whole | |
11 | can be found at: | |
12 | ||
13 | http://www.wxwidgets.org | |
14 | ||
15 | Information about the Windows CE port in particular can be found in | |
16 | the wxWinCE topic in the wxWidgets reference manual. | |
17 | ||
18 | Supported platforms | |
19 | =================== | |
20 | ||
21 | These are the supported platforms at the moment: | |
22 | ||
23 | - x86 emulator build in eVC 3 and eVC 4.x | |
24 | - Pocket PC (StrongARM) | |
25 | - Smartphone (StrongARM) | |
26 | - Windows Mobile 5 | |
27 | ||
28 | You can test the library and applications using the Pocket PC emulator | |
29 | and/or Compaq iPAQ or other PDAs using Pocket PC. | |
30 | ||
31 | Compiler installation | |
32 | ===================== | |
33 | ||
34 | 1. Embedded Visual C++ | |
35 | ---------------------- | |
36 | ||
37 | Get the Visual C++ embedded (FREE) from Microsoft website | |
38 | http://msdn.microsoft.com/vstudio/device/embedded/download.asp | |
39 | ||
40 | You must use Embedded Visual C++ 3.0 or Embedded Visual C++ 4.x. | |
41 | ||
42 | You can download the Smartphone 2002/3 and Pocket PC 2002/3 | |
43 | SDKs separately. | |
44 | ||
45 | 2. Visual Studio 2005 | |
46 | --------------------- | |
47 | ||
48 | VS 2005 Professional is required to write Windows Mobile 5 applications, although Pocket PC | |
49 | 2003 applications should also run on Mobile 5. VS 2005 must | |
50 | be purchased, and you can then download the Mobile 5 2005 SDK | |
51 | from Microsoft's site. | |
52 | ||
53 | wxWidgets/CE Configuration | |
54 | ================================ | |
55 | ||
56 | You may wish to customize the following file | |
57 | before compiling wxWinCE: | |
58 | ||
59 | include/wx/msw/wince/setup.h | |
60 | ||
61 | wxWidgets/CE Compilation | |
62 | ================================ | |
63 | ||
64 | NOTE: to generate targets not in the standard project files, | |
65 | you should rebuild the project files using Bakefile. | |
66 | Also, if you are building from a CVS version of wxWidgets, | |
67 | you need to create eVC++ project files or get them from | |
68 | somewhere, such as the daily makefile builds here: | |
69 | ||
70 | http://biolpc22.york.ac.uk/pub/CVS_Makefiles/ | |
71 | ||
72 | See technote docs/tech/tn0016.txt for details on using Bakefile, | |
73 | and you can get Bakefile from: | |
74 | ||
75 | http://bakefile.sf.net | |
76 | ||
77 | Open build/wince/wx.vcw, select an ARM or x86 target (or emulator | |
78 | target for eVC++ 4), and compile. | |
79 | ||
80 | Then open samples/minimal/minimal.vcw, select an ARM, x86 or emulator | |
81 | target, and compile. You can use the emulator or real hardware to run | |
82 | the sample. | |
83 | ||
84 | There may be long delays while eVC++ computes dependencies, and expect | |
85 | to wait a long time for loading and saving workspaces. Do not attempt to | |
86 | save the wxWidgets library project file: it will take forever and generate | |
87 | a huge file, so make alterations either using Bakefile or by editing the | |
88 | project file with a text editor, and reloading. Sample project files are OK | |
89 | to save. | |
90 | ||
91 | To compile using the emulator on eVC++3: | |
92 | ||
93 | - Open build/wince/wx.vcw, select the | |
94 | WIN32 (WCE x86) Debug Unicode configuration, close the dialog, | |
95 | then select Pocket PC 2002 and Pocket PC 2002 Emulation on the toolbar, | |
96 | and compile. | |
97 | ||
98 | - Open samples/minimal/minimal.vcw, select the | |
99 | WIN32 (WCE x86 Debug) configuration, and select Pocket PC 2002 and | |
100 | Pocket PC 2002 Emulation as before. | |
101 | ||
102 | To compile using the emulator on eVC++4: | |
103 | ||
104 | - Open build/wince/wx.vcw, select the | |
105 | WIN32 (WCE Emulator) Debug configuration, and compile. | |
106 | ||
107 | - Open samples/minimal/minimal.vcw with eVC++, select the | |
108 | WIN32 (WCE emulator) Debug configuration, and compile. | |
109 | ||
110 | Note: builds for the different SDKs (Smartphone, PPC, .Net) | |
111 | use the same directory and library names, so for the moment | |
112 | these builds cannot co-exist simultaneously. | |
113 | ||
114 | To use Visual Studio 2005, you need to allow VS to convert the projects | |
115 | first (but install all the SDKs you need to _before_ converting), and then | |
116 | you need to adjust the library settings of each wxWidgets and sample project. | |
117 | ||
118 | Edit the configuration properties for each configuration and in the Librarian, | |
119 | add a relative path ..\..\lib to each library path. For example: | |
120 | ||
121 | ..\..\lib\$(PlatformName)\$(ConfigurationName)\wx_mono.lib | |
122 | ||
123 | Then, for a sample you want to compile, edit the configuration properties | |
124 | and make sure ..\..\lib\$(PlatformName)\$(ConfigurationName) is in the Linker/General/Additional | |
125 | Library Directories property. Also change the Linker/Input/Additional Dependencies | |
126 | property to something like: | |
127 | ||
128 | coredll.lib wx_mono.lib wx_wxjpeg.lib wx_wxpng.lib wx_wxzlib.lib wx_wxexpat.lib commctrl.lib winsock.lib wininet.lib | |
129 | ||
130 | since the library names in the wxWidgets workspace were changed | |
131 | by VS 2005. | |
132 | ||
133 | Status | |
134 | ====== | |
135 | ||
136 | It's possible to create working Pocket PC or Smartphone | |
137 | applications with this port. For further information | |
138 | about how to use wxWidgets with Windows CE, and further | |
139 | work that needs to be done, see the wxWinCE topic in the | |
140 | reference manual, and also: | |
141 | ||
142 | http://wiki.wxwindows.org/wiki.pl?Developers_Notebook/WxWinCE | |
143 | ||
144 | The "Life!" demo in demos/life has some adaptations for | |
145 | wxWinCE, and also demonstrates how to make an installer for | |
146 | a Pocket PC application. | |
147 | ||
148 | Disclaimer | |
149 | ========== | |
150 | ||
151 | All product names are used for identification purposes and are trademarks | |
152 | or registered trademarks owned by their respective companies. | |
153 |