Hi Attila, Please reply on the sipxtapi dev mailing list, so everyone can benefit from this information. I've CCed the list in this reply.
sipxtapi has been ported to PocketPC 2003, Windows Mobile 5, and Windows Mobile 6, however, there are some caveats: The Windows Mobile targets in the projects have not been tested (AFAIK) since the porting effort was active, about 1.5-2 years ago PocketPC 2003 port was done with Microsoft eMbedded Visual C++ 4.0, as it is in the public domain now -- you can find these projects in the sipxtapi sources, at the base of each library -- names of the projects are sipX<name>.vcp (i.e. sipXmediaLib.vcp) Windows Mobile 5/6 port was done with Visual Studio 2005. You'll find Arm/Windows Mobile 5/6 targets in the -msvc8.vcproj projects. Here's a summary of what all the different project types we have under source control, reasonings behind them, and their testing status: - *.vcproj: Visual Studio 2003 project files. These are always up to date <Recommended for x86 windows build>. If you have a newer Visual Studio, you can import these and be good to go. - *.sln: Visual Studio 2003 solution files. See .vcproj. - *.dsp: Visual Studio 6 projects. These are always up to date. - *.dsw: Visual Studio 6 workspace. These are always up to date. - *-msvc8.vcproj: Visual Studio 2005 project files created specifically for Windows Mobile 6, with WM5 targets added a bit later. Visual Studio 2003 project files were missing some crucial features needed for cross-architecture development. These are untested under Windows Mobile. - *.vcp: Microsoft eVC4 project files, specifically for PocketPC 2003 development. These are untested under Windows Mobile. If you would like to bring Windows Mobile 5 support up-to-date, it should not be too difficult, since the porting effort has been done before. The projects will probably need to be cleaned up. Compiler options (specifically preprocessor defines) and which files are included in the library compile may need to be fixed. This has been updated since the porting effort to add new files we've added to the project, but again, hasn't been tested under Windows Mobile since the porting effort ended about 1.5-2 years ago. Quite a bit of changes have been made to sipXmediaLib since the port, so you may encounter some C++ code fixes that may need to be done there, however, in other libraries there have only been minor changes, so those should work fine. Have a look at the .vcproj files, and at the -msvc8.vcproj files, and take the new changes from the .vcproj files and apply them to the -msvc8.vcproj files. If you have any questions, give me a holler -- it's been a while, but I may be able to answer some questions. I worked on the PocketPC 2003, and the WM6 support. As for the last rev of our sources that works with the Mindows Mobile projects, we don't have that tracked. Give a look at the logs for the -msvc8.vcproj files and guestimate based on that -- r9144 is probably a good place to start. As always, the way to check out our sources is: svn co http://scm.sipfoundry.org/rep/sipX/main sipxtapi for more information on the branches we have, see the wiki page: http://sipxtapi.sipfoundry.org/wiki/SipXtapi#Branches Of course, we welcome any patches you may have. Once you have a patch ready for review send it to me using the public Rietveld install over at appspot.com: http://codereview.appspot.com/ Choose "sipXtapi/main branch" and add me (kkyzivat) as a reviewer. On Fri, Mar 20, 2009 at 6:06 PM, Attila Nyers <cipofuz...@gmail.com> wrote: > Hi! > > I would like to use sipx to develop a softphone for windows mobile 5.0. Is > it possible to build sipx on wince with visual studio 2005? if not, which is > the latest build? > > thx, > Attila > -- Keith Kyzivat SIPez LLC. SIP VoIP, IM and Presence Consulting http://www.SIPez.com tel: +1 (617) 273-4000
_______________________________________________ sipxtapi-dev mailing list sipxtapi-dev@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
