Re: [CMake] CMake doesn't detect Microsoft Build Tools 2015 on Windows 10

Please open a bug, I can take a look at it. From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Eduard Wirch Sent: Monday, October 10, 2016 02:41 To: cmake@cmake.org Subject: [CMake] CMake doesn't detect Microsoft Build Tools 2015 on Windows 10 Hi I've installed build tools from here:

Re: [cmake-developers] Problems with icons for Windows Store 10.0

Hi Roman, Glad to hear that it works. We discussed this when I implemented the feature, the only reason the functionality has been implemented is to supplement the intermediate projects that CMake produces that cannot easily be adapted for the requirements of a Windows Store application. For

Re: [CMake] [cmake-developers] Problems with icons for Windows Store 10.0

Hi Roman, Glad to hear that it works. We discussed this when I implemented the feature, the only reason the functionality has been implemented is to supplement the intermediate projects that CMake produces that cannot easily be adapted for the requirements of a Windows Store application. For

Re: [CMake] [cmake-developers] Problems with icons for Windows Store 10.0

That's most likely because you're missing an AppxManifest. In order to build the CMake detection projects, we inject some necessary files into the project when they aren't specified. This includes the manifest and the icons. Can you add your app manifest to the project (look at

Re: [CMake] Visual Studios platform choice

When Visual Studio creates a project, by default it will create it for multiple architectures. When running through CMake, only 1 platform is generated. Therefore Visual Studio shows the platform options but only the available platforms are shown. We wrote a prototype to support creating

Re: [CMake] Windows path too long

It’s a little more complicated than just saying Windows 10 and turning on a regkey. There are other changes that need to be enabled in order to get the whole scenario working. The main one being that MSBuild needs to be updated and manifested to be able to use paths longer than 260 characters.

Re: [CMake] Bash on ubuntu on windows as target

I’ve looked more in depth at the issue, and while this doesn’t work yet, we’re looking to enable this in a future Windows Insider Flight for better windows/linux interop. From: Gilles Khouzam Sent: Monday, August 15, 2016 13:24 To: 'Tiago Macarios' ; csiga.b...@aol.com

Re: [CMake] Bash on ubuntu on windows as target

That’s an interesting idea, I’m not sure why cmd is failing to invoke bash properly, but I will try and figure it out. Also, for addressing invoking bash.exe without copying it to SysWow64, you can reference it by C:\Windows\Sysnative\bash.exe from a 32-bit process. It still doesn’t make the

Re: [CMake] [Visual Studio] Universal Windows Platform projects

Hi Adam, Nagy-Egri I’ve written most of the code to support Windows Universal Apps and would be happy to help you get this working. We have some very prominent customers who are using this functionality to publish their apps and games to the Windows Store. The support is not a pilot project

Re: [cmake-developers] Patch: Add the ability to specify SDK_REFERENCES for Visual Studio

I've changed it to the Debug Universal C-Runtime which should be included with the SDK. This also leverages the version of the SDK to match the other extensions reducing the risk of failures. -Original Message- From: Brad King [mailto:brad.k...@kitware.com] Sent: Tuesday, June 21,

Re: [cmake-developers] Patch: Add the ability to specify SDK_REFERENCES for Visual Studio

I'll take a look to find an sdk that is included. Sent from my Windows 10 phone From: Brad King Sent: Tuesday, June 21, 2016 7:31 To: Gilles Khouzam Cc: cmake-developers@cmake.org Subject:

[cmake-developers] Patch: Add the ability to specify SDK_REFERENCES for Visual Studio

This patch is to add the ability with Visual Studio generators to add references to SDKs. This is similar to the DESKTOP, IOT and MOBILE extensions for Windows 10, but makes the process more generic, using the Property VS_SDK_REFERENCES as a semi-colon separated list. For example, adding a

[cmake-developers] Patch: Add ability to override the default Visual Studio tool

This patch is to add the ability to override the default tool assigned by the Visual Studio generator based on the extension, by using a new source property VS_TOOL_OVERRIDE. This also allows for new tools to be defined without having to teach CMake how to handle them. For example, this allows