]> git.saurik.com Git - wxWidgets.git/blame - docs/msw/wince/readme.txt
Added documentation for compiling under Windows Mobile 5
[wxWidgets.git] / docs / msw / wince / readme.txt
CommitLineData
1a4fe894
JS
1
2 =================================================
6fdaa477 3 Welcome to wxWidgets/CE 2.7.0
1a4fe894
JS
4 =================================================
5
6fdaa477 6You have downloaded version 2.7.0 of the Windows CE port of
f4dea58d 7the wxWidgets GUI library. This runs on Pocket PC 2002/2003,
6fdaa477 8Smartphone 2002/2003, Windows CE .NET 4.x, and Windows Mobile 5.
1a4fe894 9
fc2171bd 10More information about the wxWidgets project as a whole
1a4fe894
JS
11can be found at:
12
fc2171bd 13 http://www.wxwidgets.org
1a4fe894 14
f4dea58d
JS
15Information about the Windows CE port in particular can be found in
16the wxWinCE topic in the wxWidgets reference manual.
1a4fe894
JS
17
18Supported platforms
19===================
20
a96b4743 21These are the supported platforms at the moment:
93f467a3 22
be076b78 23- x86 emulator build in eVC 3 and eVC 4.x
f4dea58d
JS
24- Pocket PC (StrongARM)
25- Smartphone (StrongARM)
6fdaa477 26- Windows Mobile 5
1a4fe894 27
f4dea58d
JS
28You can test the library and applications using the Pocket PC emulator
29and/or Compaq iPAQ or other PDAs using Pocket PC.
1a4fe894 30
1a4fe894
JS
31Compiler installation
32=====================
33
6fdaa477
JS
341. Embedded Visual C++
35----------------------
36
1a4fe894
JS
37Get the Visual C++ embedded (FREE) from Microsoft website
38 http://msdn.microsoft.com/vstudio/device/embedded/download.asp
39
a96b4743 40You must use Embedded Visual C++ 3.0 or Embedded Visual C++ 4.x.
a96b4743 41
f4dea58d
JS
42You can download the Smartphone 2002/3 and Pocket PC 2002/3
43SDKs separately.
6fdaa477
JS
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.
f4dea58d 52
fc2171bd 53wxWidgets/CE Configuration
a96b4743
JS
54================================
55
56You may wish to customize the following file
57before compiling wxWinCE:
58
59include/wx/msw/wince/setup.h
1a4fe894 60
fc2171bd 61wxWidgets/CE Compilation
1a4fe894
JS
62================================
63
a6966de1
JS
64NOTE: to generate targets not in the standard project files,
65you should rebuild the project files using Bakefile.
8c9f8f91
JS
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
be076b78 76
f4dea58d
JS
77Open build/wince/wx.vcw, select an ARM or x86 target (or emulator
78target for eVC++ 4), and compile.
1a4fe894 79
f4dea58d
JS
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.
1a4fe894 83
f4dea58d
JS
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.
1cc0bc10
JS
90
91To compile using the emulator on eVC++3:
92
a6966de1 93- Open build/wince/wx.vcw, select the
1cc0bc10
JS
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
be076b78 98- Open samples/minimal/minimal.vcw, select the
43499aa4
JS
99 WIN32 (WCE x86 Debug) configuration, and select Pocket PC 2002 and
100 Pocket PC 2002 Emulation as before.
1cc0bc10
JS
101
102To compile using the emulator on eVC++4:
103
a6966de1 104- Open build/wince/wx.vcw, select the
f4dea58d 105 WIN32 (WCE Emulator) Debug configuration, and compile.
1cc0bc10 106
f4dea58d 107- Open samples/minimal/minimal.vcw with eVC++, select the
1cc0bc10
JS
108 WIN32 (WCE emulator) Debug configuration, and compile.
109
8c9f8f91 110Note: builds for the different SDKs (Smartphone, PPC, .Net)
f686d43e
JS
111use the same directory and library names, so for the moment
112these builds cannot co-exist simultaneously.
113
6fdaa477
JS
114To use Visual Studio 2005, you need to allow VS to convert the projects
115first, and then you need to adjust the library settings of
116each 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..\$(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
1a4fe894
JS
133Status
134======
135
f4dea58d 136It's possible to create working Pocket PC or Smartphone
280e0cc4 137applications with this port. For further information
f4dea58d
JS
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:
1a4fe894 141
a96b4743 142http://wiki.wxwindows.org/wiki.pl?Developers_Notebook/WxWinCE
1a4fe894 143
f4dea58d
JS
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
1a4fe894
JS
148Disclaimer
149==========
150
151All product names are used for identification purposes and are trademarks
152or registered trademarks owned by their respective companies.
153