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
Thanks Gilles,
I added a custom appxmanifest as you mentioned and it works, but it would
nevertheless very helpful to customize such things via variables and let CMake
fill out the rest.
Regards
Roman
> Am 05.10.2016 um 21:19 schrieb Gilles Khouzam :
>
> That's most likely because you're miss
Craig Scott wrote:
> I'm coming in half way to this discussion, so apologies if my comments
> interspersed below are not so well related to the core topic of
> discussion.
Hi Craig,
Thanks for your input.
> Consider the following example which perhaps better shows that this
> problem may not be
I'm coming in half way to this discussion, so apologies if my comments
interspersed below are not so well related to the core topic of discussion.
On Thu, Oct 6, 2016 at 9:38 AM, Stephen Kelly wrote:
> Brad King wrote:
>
> > The scoping doesn't
> > match the generator semantics exactly, but it i
Brad King wrote:
> On 10/04/2016 05:46 PM, Stephen Kelly wrote:
>> This causes problems because now the code has to read the value for each
>> directory and can't assume that the value is always the same as the value
>> from the top-level CMakeLists file.
>
> Many of these are honored only in the
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
Tests\VSWinStore
Hi Brad,
I am sorry, but I have to take up this subject again.
I want to include Vc (sometimes called Vc-Devel) as an optional
dependency. Vc provides a ConfigVc.cmake.
1. When I use "find_package(Vc)", many users get warnings that neither
FindVc.cmake nor VcConfig.cmake is found. The warning loo
On 10/05/2016 02:56 PM, Roman Wüger wrote:
> I tried the following to copy the required app icons to the required
> destination:
>
> configure_file(Logo.png
> ${CMAKE_CURRENT_BINARY_DIR}/${PROJECT_NAME}.dir/Logo.png COPYONLY)
That's a CMake-private directory whose location is an implementation
Hello,
I tried the following to copy the required app icons to the required
destination:
configure_file(Logo.png
${CMAKE_CURRENT_BINARY_DIR}/${PROJECT_NAME}.dir/Logo.png COPYONLY)
The CMake process itself overrides those files at the end with the files from
the CMake's Template directory, whi
On 10/04/2016 05:46 PM, Stephen Kelly wrote:
> This causes problems because now the code has to read the value for each
> directory and can't assume that the value is always the same as the value
> from the top-level CMakeLists file.
Many of these are honored only in the top-level directory anyw
On 04.10.2016 11:20, Tobias Hunger wrote:
On Mo, 2016-10-03 at 14:25 -0400, Brad King wrote:
The list we need would thus be built up to contain all COMMAND
arguments to add_test that are also build targets in CMake.
The list would also need to include targets mentioned in generator
expressions
Le 04/10/16 à 22:32, Robert Maynard a écrit :
I am proud to announce the first CMake 3.7 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.7
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.7/r
12 matches
Mail list logo