behaviour.
For building instructions, see docs/msw/wince in the
-distribution. The rest of this section documents issues you
+distribution, also the section about Visual Studio 2005 project
+files below. The rest of this section documents issues you
need to be aware of when programming for Windows CE devices.
\subsubsection{General issues for wxWinCE programming}
wxwince26d.lib(control.obj) : error LNK2001: unresolved external symbol "const type_info::`vftable'" (??_7type_info@@6B@)
\end{verbatim}
+\wxheading{Windows Mobile 5.0 emulator}
+
+Note that there is no separate emulator configuration for Windows Mobile 5.0: the
+emulator runs the ARM code directly.
+
+\wxheading{Visual Studio 2005 project files}
+
+Unfortunately, Visual Studio 2005, required to build Windows Mobile 5.0 applications,
+doesn't do a perfect job of converting the project files from eVC++ format.
+
+When you have converted the wxWidgets workspace, edit the configuration properties
+for each configuration and in the Librarian, add a relative path ..\..\lib to
+each library path. For example: {\tt ..\$(PlatformName)\$(ConfigurationName)\wx_mono.lib}.
+
+Then, for a sample you want to compile, edit the configuration properties
+and make sure {\tt ..\..\lib\$(PlatformName)\$(ConfigurationName)} is in the Linker/General/Additional
+Library Directories property. Also change the Linker/Input/Additional Dependencies
+property to something like {\tt 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).
+
+Alternately, you could could edit all the names to be identical to the original eVC++
+names, but this will probably be more fiddly.
+
\subsubsection{Remaining issues}
These are some of the remaining problems to be sorted out, and features
\itemsep=0pt
\begin{itemize}
-\item {\bf Font dialog.} The generic font dialog is currently used, which
-needs to be simplified (and speeded up).
+\item {\bf Windows Mobile 5 issues.} It is not possible to get the HMENU for
+the command bar on Mobile 5, so the menubar functions need to be rewritten
+to get the individual menus without use of a menubar handle. Also the
+new Mobile 5 convention of using only two menus (and no bitmap buttons) needs to be
+considered.
\item {\bf Sizer speed.} Particularly for dialogs containing notebooks,
layout seems slow. Some analysis is required.
\item {\bf Notification boxes.} The balloon-like notification messages, and their
a specified location.
\item {\bf Further abstraction.} We should be able to abstract away more of the differences
between desktop and mobile applications, in particular for sizer layout.
+\item {\bf Dialog captions.} The blue, bold captions on dialogs - with optional help button -
+should be catered for, either by hard-wiring the capability into all dialogs and panels,
+or by providing a standard component and sizer.
\end{itemize}
=================================================
- Welcome to wxWidgets/CE 2.6.2
+ Welcome to wxWidgets/CE 2.7.0
=================================================
-You have downloaded version 2.6.2 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:
- 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
=====================
+1. Embedded Visual C++
+----------------------
+
Get the Visual C++ embedded (FREE) from Microsoft website
http://msdn.microsoft.com/vstudio/device/embedded/download.asp
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
================================
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, 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
======
projects / wxWidgets.git / commitdiff
