@gurry In my opinion, porting
libstd to use APIs provided by the different winapi family will be the hardest part, and I imagine would probably take a month, or more. Adding targets for the ARM architecture used by Windows phone should be maybe a week, although this part doesn’t need to be done right away as the Windows Phone Emulator uses Hyper-V so it is an x86 version of Windows Phone. Adding support for invoking the linker correctly to target Windows phone should be a week. If creating a phone app requires implementing some COM interface, then tack on another month.
I don’t know of any guides, but if you ask on IRC, I’m sure there are plenty of people who can help with adding targets.
I think one of the things we really need is to decide on how to deal with winapi families in the first place. The best solution I can think of at the moment is having a different set of targets for each family. There are five families (desktop app, pc app, phone app, system, and server), and the current
arch-pc-windows-msvc targets correspond to the desktop app family. I’m thinking it would probably be better to modify the
pc part rather than the