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 cbd37b0f80fe2c21de6f29df6a18eb58cbd1b7ff..17cefa6e69a66d040a8b10bb8d9fe795691e6cb2 100644 (file)
--- a/docs/msw/wince/readme.txt
+++ b/docs/msw/wince/readme.txt
@@ -1,11 +1,11 @@
 
   =================================================
-  Welcome to wxWidgets/CE 2.5.4
+  Welcome to wxWidgets/CE 2.7.0
   =================================================
 
-You have downloaded version 2.5.4 of the Windows CE port of
+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, and Windows CE .NET 4.x.
+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:
@@ -23,6 +23,7 @@ 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.
@@ -30,6 +31,9 @@ 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
  
@@ -37,6 +41,14 @@ 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.
  
 wxWidgets/CE Configuration
 ================================
@@ -51,7 +63,16 @@ wxWidgets/CE Compilation
 
 NOTE: to generate targets not in the standard project files,
 you should rebuild the project files using Bakefile.
-See technote docs/tech/tn0016.txt for details.
+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:
+
+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
 
 Open build/wince/wx.vcw, select an ARM or x86 target (or emulator
 target for eVC++ 4), and compile.
@@ -86,6 +107,29 @@ To compile using the emulator on eVC++4:
 - 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
 ======