WindowsMobileDevices

An effort is underway to get O2S running on Windows Mobile-based devices, such as the O2 Xda Atom and HP iPAQ rw6815. This page provides some information pertinent to that effort.

Software

JustPlay

• AudioDemo [svn://o2s.csail.mit.edu/trunk/o2s/hosts/wince/AudioDemo]

  • Example audio-capture application, written in C#

• JustPlayVoiceRemote [svn://o2s.csail.mit.edu/trunk/o2s/hosts/wince/JustPlayVoiceRemote]

  • Push-to-talk voice remote application, written in C. Uses Bonjour to discover a remote voice-remote server, and transmits audio to it.

• o2s-libs for Windows CE [svn://o2s.csail.mit.edu/trunk/o2s-libs/dist/wince]

  • All-in-one package for O2S dependencies. Still under development.

Third Party

• PythonCE

  • A very nice port of Python 2.5 to Windows CE

• wxPython for PythonCE

  • Port of wxPython to Windows CE. Looks to be in the early stages of development, but worth keeping an eye on.

Development

Documentation

• Introduction to Development Tools for Windows Mobile-based Devices

  • Explains the various tools available for Windows Mobile development. Worth reading before you install any of the tools.

• How to: Connect to Windows CE Device Without ActiveSync

  • Useful if you need to debug an application that does network I/O, since ActiveSync disables most network interfaces

• Implementing a Network Service on Windows CE

  • How system services are implemented on Windows CE. Mainly of interest for porting Bonjour to CE.

• Windows CE / Windows Mobile Versions

  • A detailed history of and guide to Windows CE versions, which can be very confusing

• Windows Mobile Team Blog

  • Good source for random but valuable info on Windows Mobile development

• MSDN Library

  • The primary resource for Windows programmers. Very thorough, but difficult to navigate.

Tools

MSDN has a guide describing how to install Windows CE development tools. The section "To install the development tools in the correct order" describes the order in which the various packages should be installed. For O2S development, it should be sufficient to perform steps 1, 3, 5, 10, and 11 in this list, or just install the tools described below in the order they're listed.

• ActiveSync

  • Interface between a Windows Mobile device and a Windows PC. Necessary for installing third-party software and deploying/debugging your own.

• eMbedded Visual C++ 4.0

  • Although Microsoft now recommends Visual Studio for all Windows Mobile development, some packages (notably PythonCE) still rely on eMbedded Visual C++, so it's worth installing in case you have to build them. You'll also need to install the following components:

    • eMbedded Visual C++ 4.0 SP4

    • SDK for Windows Mobile 2003-based Pocket PCs

• Visual Studio 2005

  • Microsoft's primary development suite, which you'll want if you're developing for any Windows platform. In addition, you should install the following:

    • Visual Studio 2005 Service Pack 1

      • Adds support for Windows Mobile 6, which could be useful in the future

    • Windows Mobile 5.0 Developer Resource Kit

      • Provides the Pocket PC and Smartphone SDKs. Note that it only installs the installers for the SDKs, which have to be run manually. The installers are located in C:\Program Files\Windows Mobile 5.0 Developer Resource Kit\content\Developer Tools\Windows Mobile 5.0 SDKs

• Remote Display Control for Pocket PC (optional)

  • Allows you to drive a Windows Mobile device from your desktop machine. Can be handy, although there's a lot of interface lag.