Correct 'markup' for GetResourceHandle after recent change in wx/gdiobj.h.

[wxWidgets.git] / docs / msw / wince / readme.txt

diff --git a/docs/msw/wince/readme.txt b/docs/msw/wince/readme.txt
index 030f8551a1c0dc978b6dd84dcbef88d601ea20e2..17cefa6e69a66d040a8b10bb8d9fe795691e6cb2 100644 (file)
--- a/docs/msw/wince/readme.txt
+++ b/docs/msw/wince/readme.txt
@@ -1,70 +1,149 @@
 
   =================================================
 
   =================================================

-  Welcome to wxWindows/CE 2.3.4 (is becoming 2.5.0)
+  Welcome to wxWidgets/CE 2.7.0

   =================================================
 
   =================================================
 

-You have downloaded version 2.3.4 of the WinCE 3.0 port of
-the wxWindows GUI library. This runs on WindowsCE 3.0.
+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 wxWindows project as a whole
+More information about the wxWidgets project as a whole

 can be found at:
 
 can be found at:
 

-  http://www.wxwindows.org
+  http://www.wxwidgets.org

 
 

+Information about the Windows CE port in particular can be found in
+the wxWinCE topic in the wxWidgets reference manual.

 
 Supported platforms
 ===================
 
 
 Supported platforms
 ===================
 

-These are the supported platform at the moment
-- x86 emulator
-- PocketPC (StrongARM)
-
-You can test the library and applications using PocketPC emulator 
-and/or Compaq iPAQ or other PDAs using PocketPC
-
-WindowsCE.NET is not supported.
+These are the supported platforms at the moment:

 
 

+- 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 the Pocket PC emulator 
+and/or Compaq iPAQ or other PDAs using Pocket PC.

 
 Compiler installation
 =====================
 
 
 Compiler installation
 =====================
 

+1. Embedded Visual C++
+----------------------
+

 Get the Visual C++ embedded (FREE) from Microsoft website
  http://msdn.microsoft.com/vstudio/device/embedded/download.asp
  
 Get the Visual C++ embedded (FREE) from Microsoft website
  http://msdn.microsoft.com/vstudio/device/embedded/download.asp
  

-You must use Visual Tools 3.0 for CE 3.0 
- (this is the same we are currently using for wxWinCE) 
+You must use Embedded Visual C++ 3.0 or Embedded Visual C++ 4.x.
+
+You can download the Smartphone 2002/3 and Pocket PC 2002/3
+SDKs separately.
+
+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.

  
  

-Install selecting only the two target platforms used:
-- WCE x86em (PocketPC emulation)
-- WCE ARM (PocketPC StrongARM)
+wxWidgets/CE Configuration
+================================

 
 

+You may wish to customize the following file
+before compiling wxWinCE:

 
 

+include/wx/msw/wince/setup.h

 
 

-General installation notes
-==========================
+wxWidgets/CE Compilation
+================================

 
 

-Alter your WXWIN environment variable to point to the root directory of the
-wxWindows installation.
+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:

 
 

-Add wxWindows include and library paths into Tools-Options-Directories
+http://biolpc22.york.ac.uk/pub/CVS_Makefiles/

 
 

+See technote docs/tech/tn0016.txt for details on using Bakefile,
+and you can get Bakefile from:

 
 

+http://bakefile.sf.net

 
 

-wxWindows/CE Compilation
-================================
+Open build/wince/wx.vcw, select an ARM or x86 target (or emulator
+target for eVC++ 4), and compile.
+
+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 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:

 
 

-The following sections explain how to compile wxWindows/CE with the 
-Visual C++ embedded compiler.
+- 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/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 build/wince/wx.vcw, select the
+  WIN32 (WCE Emulator) Debug configuration, and compile.
+
+- 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
 ======
 
 
 Status
 ======
 

-Currently develompment
+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
 ==========
 
 Disclaimer
 ==========


@@ -72,9 +151,3 @@ Disclaimer
 All product names are used for identification purposes and are trademarks 
 or registered trademarks owned by their respective companies.
 
 All product names are used for identification purposes and are trademarks 
 or registered trademarks owned by their respective companies.
 

-
-
-  Marco Cavallini
-www.koansoftware.com
-
-.eof.