docs/msw/wince/readme.txt

   1
   2   =================================================
   3   Welcome to wxWidgets/CE 2.5.4
   4   =================================================
   5
   6 You have downloaded version 2.5.4 of the Windows CE port of
   7 the wxWidgets GUI library. This runs on Pocket PC 2002/2003,
   8 Smartphone 2002/2003, and Windows CE .NET 4.x.
   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
  27 You can test the library and applications using the Pocket PC emulator
  28 and/or Compaq iPAQ or other PDAs using Pocket PC.
  29
  30 Compiler installation
  31 =====================
  32
  33 Get the Visual C++ embedded (FREE) from Microsoft website
  34  http://msdn.microsoft.com/vstudio/device/embedded/download.asp
  35
  36 You must use Embedded Visual C++ 3.0 or Embedded Visual C++ 4.x.
  37
  38 You can download the Smartphone 2002/3 and Pocket PC 2002/3
  39 SDKs separately.
  40
  41 wxWidgets/CE Configuration
  42 ================================
  43
  44 You may wish to customize the following file
  45 before compiling wxWinCE:
  46
  47 include/wx/msw/wince/setup.h
  48
  49 wxWidgets/CE Compilation
  50 ================================
  51
  52 NOTE: to generate targets not in the standard project files,
  53 you should rebuild the project files using Bakefile.
  54 See technote docs/tech/tn0016.txt for details.
  55
  56 Open build/wince/wx.vcw, select an ARM or x86 target (or emulator
  57 target for eVC++ 4), and compile.
  58
  59 Then open samples/minimal/minimal.vcw, select an ARM, x86 or emulator
  60 target, and compile. You can use the emulator or real hardware to run
  61 the sample.
  62
  63 There may be long delays while eVC++ computes dependencies, and expect
  64 to wait a long time for loading and saving workspaces. Do not attempt to
  65 save the wxWidgets library project file: it will take forever and generate
  66 a huge file, so make alterations either using Bakefile or by editing the
  67 project file with a text editor, and reloading. Sample project files are OK
  68 to save.
  69
  70 To compile using the emulator on eVC++3:
  71
  72 - Open build/wince/wx.vcw, select the
  73   WIN32 (WCE x86) Debug Unicode configuration, close the dialog,
  74   then select Pocket PC 2002 and Pocket PC 2002 Emulation on the toolbar,
  75   and compile.
  76
  77 - Open samples/minimal/minimal.vcw, select the
  78   WIN32 (WCE x86 Debug) configuration, and select Pocket PC 2002 and
  79   Pocket PC 2002 Emulation as before.
  80
  81 To compile using the emulator on eVC++4:
  82
  83 - Open build/wince/wx.vcw, select the
  84   WIN32 (WCE Emulator) Debug configuration, and compile.
  85
  86 - Open samples/minimal/minimal.vcw with eVC++, select the
  87   WIN32 (WCE emulator) Debug configuration, and compile.
  88
  89 Note: compiles for the different SDKs (Smartphone, PPC, .Net)
  90 use the same directory and library names, so for the moment
  91 these builds cannot co-exist simultaneously.
  92
  93 Status
  94 ======
  95
  96 It's possible to create working Pocket PC or Smartphone
  97 applications with this port. For further information
  98 about how to use wxWidgets with Windows CE, and further
  99 work that needs to be done, see the wxWinCE topic in the
 100 reference manual, and also:
 101
 102 http://wiki.wxwindows.org/wiki.pl?Developers_Notebook/WxWinCE
 103
 104 The "Life!" demo in demos/life has some adaptations for
 105 wxWinCE, and also demonstrates how to make an installer for
 106 a Pocket PC application.
 107
 108 Disclaimer
 109 ==========
 110
 111 All product names are used for identification purposes and are trademarks
 112 or registered trademarks owned by their respective companies.
 113