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