<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Thanks for the response Brad. Comments inline below...<br><br>Paul.<div><br><div>> Date: Mon, 15 Jul 2013 08:38:11 -0400<br>> From: brad.king@kitware.com<br>> To: cmake-developers@cmake.org<br>> Subject: Re: [cmake-developers] Working towards Windows Phone 8 support<br>> <br>> On 07/12/2013 07:58 AM, Paul Annetts wrote:<br>> > I'm interested in contributing towards Windows Phone 8 support in<br>> > CMAKE, i.e. http://public.kitware.com/Bug/view.php?id=13791<br>> <br>> Thanks for working on this. Consider drawing attention to your<br>> work by posting in the issue tracker too. I haven't personally<br>> worked on any wp80 development so it will be helpful to recruit<br>> others to help review the work.<br><div><br></div><div>Ok - I'll make a post to the tracker.</div></div><div><br></div><div>> <br>> > new "Visual Studio 11 Windows Phone 8" generator</div><div>> <br>> Our convention is to have no spaces in the name of the architecture,<br>> so a name like "Visual Studio 11 WP8" will be better. Some projects<br>> use regular expressions to parse the generator name so we should<br>> stick to that convention.<br><br></div><div>No problem.<br></div><div><br></div><div>> <br>> > 1. Targets the Windows Phone 8 platform toolset (v110_wp80).<br>> <br>> See the CMAKE_GENERATOR_TOOLSET feature added in 2.8.11 along with<br>> the -T command-line option to set it.</div><div><br></div><div>I wasn’t aware of that: yes I'll take a look at that.<br></div><div><br>> <br>> > 2. Has content that allows MSBUILD/Visual Studio to build a<br>> > .lib target for either Win32 (x86 emulator) and ARM (devices) platforms.<br>> <br>> Do you mean multiple architectures in one vcxproj file?</div><div><br></div><div><div class="PlainText">Yes. There are only 2 possible architectures for WP8, it isn’t WinCE with a plethora of different CPU options. This is all cross-compilation anyhow: even if you pick the x86 platform the ABIs differ to Windows Desktop. As x86 support is designed solely to emulate the ARM phones, I believe that the platform API can be relied on to be the same between architectures.</div><div class="PlainText"><br></div><div class="PlainText">I can see the following advantages in this case:</div><ul><li><div class="PlainText">this is what the VCXPROJ files you would create in Visual Studio have, so it is a closer match to non-CMAKE projects.</div></li><li><div class="PlainText">It gives a better developer user experience - it makes it possible to switch between emulator and device without having to run CMAKE twice and open a new project. </div></li><li><div class="PlainText">This allows non-CMAKE generated WP8 Visual Studio projects to integrate properly with the CMAKE generated ones. </div></li><li><div class="PlainText">It is an approach which may be applicable to Windows Store apps as well (although I've not got much experience of that myself).</div></li></ul><div class="PlainText"><br></div><div class="PlainText">The extension of the VS10 target generator to support this is the largest change in the patch.</div><div class="PlainText"><br></div>> <br>> > How should I go about getting my work reviewed at an early stage?<br>> <br>> If the patch series is relatively small you can just use<br>> "git format-patch" and post the patches to this list.<br>> <br>> Alternatively, if the topic is large, we publish mirrors of the<br>> Git repo:<br>> <br>> https://github.com/Kitware/CMake<br>> http://gitorious.org/cmake/cmake<br>> <br>> If you have an account on one of those you can fork/clone the<br>> project there, publish your topic to your own account, and then<br>> post a link here.<br>> </div><div><br></div><div>OK - I think this is patch sized for now, but thanks for the pointers to github and gitorious.<br><br></div></div> </div></body>
</html>