In readme.wince there are not enough hints how to setup a wince development tool chain, which are required for building and testing dbus on wince. In principle building dbus on wince is possible at least with microsoft tools and with cegcc http://cegcc.sourceforge.net/ on cygwin. Compiling a small wince arm application with cegcc has been tested. Emulating wince devices seems to be possible with microsoft device emulator http://www.microsoft.com/en-us/download/details.aspx?id=5352 The device emulator needs images; a few are listed here: Windows Mobile 5 http://download.microsoft.com/download/c/b/b/cbb8bc58-07b9-46bb-86ba-d12bb0d9b1d9/efp.msi Windows Mobile 2003 http://www.microsoft.com/en-us/download/details.aspx?id=13022 Windows Mobile 6 http://www.microsoft.com/en-us/download/details.aspx?id=7974 Windows Mobile 6.1 http://www.microsoft.com/en-us/download/details.aspx?id=16182 Windows Mobile 6.1.4 http://www.microsoft.com/en-us/download/details.aspx?id=9263 Windows Mobile 6.5 http://www.microsoft.com/en-us/download/details.aspx?id=17284 For cmake there are some hints how to configure for cross compiling http://www.cmake.org/pipermail/cmake/2010-April/036318.html but this seems rather incomplete. If someone have already a receipt for a working build tool chauin installation on linux/windows please add related notes here, so a complete readme.wince could be provided.
(In reply to comment #0) > In principle building dbus on wince is possible at least with microsoft tools > and with cegcc http://cegcc.sourceforge.net/ on cygwin. Windows Phone 8 is apparently based on the WinNT kernel, not the WinCE kernel like Windows Phone 7, so Windows CE support might become less interesting over time? (Having said that, most of the WinCE-specifics in D-Bus seem to be avoiding missing library features, rather than missing kernel features, so perhaps a separate Windows Phone target will still be needed.)
Resolving WONTFIX since nobody seems to care about CE any more.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.