=================================================
- Welcome to wxWidgets/CE 2.5.2
+ Welcome to wxWidgets/CE 2.7.0
=================================================
-You have downloaded version 2.5.2 of the Windows CE port of
-the wxWidgets GUI library. This runs on PocketPC 2002,
-SmartPhone 2002, and Windows CE .NET 4.x.
+You have downloaded version 2.7.0 of the Windows CE port of
+the wxWidgets GUI library. This runs on Pocket PC 2002/2003,
+Smartphone 2002/2003, Windows CE .NET 4.x, and Windows Mobile 5.
More information about the wxWidgets project as a whole
can be found at:
http://www.wxwidgets.org
-Information about the Windows CE port in particular
-can be found here:
-
-http://wiki.wxwindows.org/wiki.pl?Developers_Notebook/WxWinCE
+Information about the Windows CE port in particular can be found in
+the wxWinCE topic in the wxWidgets reference manual.
Supported platforms
===================
These are the supported platforms at the moment:
-- x86 emulator
-- PocketPC (StrongARM)
+- x86 emulator build in eVC 3 and eVC 4.x
+- Pocket PC (StrongARM)
+- Smartphone (StrongARM)
+- Windows Mobile 5
-You can test the library and applications using PocketPC emulator
-and/or Compaq iPAQ or other PDAs using PocketPC
+You can test the library and applications using the Pocket PC emulator
+and/or Compaq iPAQ or other PDAs using Pocket PC.
Compiler installation
=====================
+1. Embedded Visual C++
+----------------------
+
Get the Visual C++ embedded (FREE) from Microsoft website
http://msdn.microsoft.com/vstudio/device/embedded/download.asp
You must use Embedded Visual C++ 3.0 or Embedded Visual C++ 4.x.
-
-Install selecting only the two target platforms used:
-- WCE x86em (PocketPC emulation)
-- WCE ARM (PocketPC StrongARM)
+You can download the Smartphone 2002/3 and Pocket PC 2002/3
+SDKs separately.
-You can install other targets but you will need
-to create new configurations for them in the
-wxWidgets project files.
+2. Visual Studio 2005
+---------------------
+VS 2005 Professional is required to write Windows Mobile 5 applications, although Pocket PC
+2003 applications should also run on Mobile 5. VS 2005 must
+be purchased, and you can then download the Mobile 5 2005 SDK
+from Microsoft's site.
+
wxWidgets/CE Configuration
================================
include/wx/msw/wince/setup.h
-These are some of the Windows CE-specific settings
-you can adjust.
-
-wxUSE_POCKETPC_UI
+wxWidgets/CE Compilation
+================================
- If you are compiling with Windows CE .NET, you may
- wish to emulate PocketPC behaviour (set it to 1), or
- take advantage of the greater flexibility of
- Windows CE .NET (set it to 0).
- If 0, the PocketPC-specific toolbar class will be
- used, which uses commandbar to combine the toolbar
- and menubar in one control. If 1, the normal menubar
- and toolbar behaviour will be used, as per
- desktop Windows.
+NOTE: to generate targets not in the standard project files,
+you should rebuild the project files using Bakefile.
+Also, if you are building from a CVS version of wxWidgets,
+you need to create eVC++ project files or get them from
+somewhere, such as the daily makefile builds here:
-wxUSE_SMARTPHONE
+http://biolpc22.york.ac.uk/pub/CVS_Makefiles/
- Set this to 1 if you wish to compile for the SmartPhone
- platform (with eVC++ 3).
+See technote docs/tech/tn0016.txt for details on using Bakefile,
+and you can get Bakefile from:
-wxWidgets/CE Compilation
-================================
+http://bakefile.sf.net
-Open src/msw/wince/wxWidgetsCE.vcp, select an
-ARM or x86 target (or emulator target for eVC++ 4),
-and compile.
+Open build/wince/wx.vcw, select an ARM or x86 target (or emulator
+target for eVC++ 4), and compile.
-Then open samples/minimal/minimalCE.vcp, select an
-ARM, x86 or emulator target, and compile. You can
-use the emulator or real hardware to run the
-sample.
+Then open samples/minimal/minimal.vcw, select an ARM, x86 or emulator
+target, and compile. You can use the emulator or real hardware to run
+the sample.
-There may be long delays while VC++ computes dependencies, and expect
-to wait a long time for loading and saving the workspace.
+There may be long delays while eVC++ computes dependencies, and expect
+to wait a long time for loading and saving workspaces. Do not attempt to
+save the wxWidgets library project file: it will take forever and generate
+a huge file, so make alterations either using Bakefile or by editing the
+project file with a text editor, and reloading. Sample project files are OK
+to save.
To compile using the emulator on eVC++3:
-- Open src/msw/wince/wxWidgetsCE.vcp, select the
+- Open build/wince/wx.vcw, select the
WIN32 (WCE x86) Debug Unicode configuration, close the dialog,
then select Pocket PC 2002 and Pocket PC 2002 Emulation on the toolbar,
and compile.
-- Open samples/minimal/minimalCE.vcp, select the
- WIN32 (WCE x86 Debug) configuration, select Pocket PC 2002 and
- Pocket PC 2002 Emulation as before, and compile.
+- Open samples/minimal/minimal.vcw, select the
+ WIN32 (WCE x86 Debug) configuration, and select Pocket PC 2002 and
+ Pocket PC 2002 Emulation as before.
To compile using the emulator on eVC++4:
-- Open src/msw/wince/wxWidgetsCE.vcp, select the
- WIN32 (WCE Emulator) Debug Unicode configuration, and compile.
+- Open build/wince/wx.vcw, select the
+ WIN32 (WCE Emulator) Debug configuration, and compile.
-- Open samples/minimal/minimalCE.vcp with eCV 4.0, select the
+- Open samples/minimal/minimal.vcw with eVC++, select the
WIN32 (WCE emulator) Debug configuration, and compile.
+Note: builds for the different SDKs (Smartphone, PPC, .Net)
+use the same directory and library names, so for the moment
+these builds cannot co-exist simultaneously.
+
+To use Visual Studio 2005, you need to allow VS to convert the projects
+first (but install all the SDKs you need to _before_ converting), and then
+you need to adjust the library settings of each wxWidgets and sample project.
+
+Edit the configuration properties for each configuration and in the Librarian,
+add a relative path ..\..\lib to each library path. For example:
+
+..\$(PlatformName)\$(ConfigurationName)\wx_mono.lib
+
+Then, for a sample you want to compile, edit the configuration properties
+and make sure ..\..\lib\$(PlatformName)\$(ConfigurationName) is in the Linker/General/Additional
+Library Directories property. Also change the Linker/Input/Additional Dependencies
+property to something like:
+
+coredll.lib wx_mono.lib wx_wxjpeg.lib wx_wxpng.lib wx_wxzlib.lib wx_wxexpat.lib commctrl.lib winsock.lib wininet.lib
+
+since the library names in the wxWidgets workspace were changed
+by VS 2005.
+
Status
======
-Currently under development. For further information
-about what has been done and what needs to be
-done, see:
+It's possible to create working Pocket PC or Smartphone
+applications with this port. For further information
+about how to use wxWidgets with Windows CE, and further
+work that needs to be done, see the wxWinCE topic in the
+reference manual, and also:
http://wiki.wxwindows.org/wiki.pl?Developers_Notebook/WxWinCE
+The "Life!" demo in demos/life has some adaptations for
+wxWinCE, and also demonstrates how to make an installer for
+a Pocket PC application.
+
Disclaimer
==========
projects / wxWidgets.git / blobdiff