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 a user's project, the AppXManifest is a critical piece that describes the application. There are some fields that need to be appropriately set (publisher Id, application name and version), even the icons need to be properly specified unless you use the exact same name for the files and don't look at having different tile sizes. For prototyping this might seem like an unnecessary step, but once you start customizing the parts of the application, it seems counter intuitive to have customizations only apply under certain conditions. Perhaps a better solution would be to give an error message if any of the defaults are replaced but a manifest is not specified. -----Original Message----- From: Roman Wüger [mailto:roman.wue...@gmx.at] Sent: Wednesday, October 5, 2016 22:39 To: Gilles Khouzam <gilles.khou...@microsoft.com> Cc: Brad King <brad.k...@kitware.com>; CMake Developer MailingList <cmake-developers@cmake.org>; CMake MailingList <cm...@cmake.org> Subject: Re: [cmake-developers] Problems with icons for Windows Store 10.0 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 <gilles.khou...@microsoft.com>: > > 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\VSWinStorePhone if you want an example) and the icons should not be > overridden then. > > Thanks > > -----Original Message----- > From: Brad King [mailto:brad.k...@kitware.com] > Sent: Wednesday, October 5, 2016 12:09 > To: Roman Wüger <roman.wue...@gmx.at>; Gilles Khouzam > <gilles.khou...@microsoft.com> > Cc: CMake Developer MailingList <cmake-developers@cmake.org>; CMake > MailingList <cm...@cmake.org> > Subject: Re: [cmake-developers] Problems with icons for Windows Store > 10.0 > >> 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 detail. > Some other interface for configuring this behavior will be needed. > >> The CMake process itself overrides those files at the end with the >> files from the CMake's Template directory, which are empty. > > From the current implementation it doesn't look like there is anyway to > prevent that. We'll need to have some configuration of where it gets those > files. > >> So, how could I use my icon files and/or what is the preferred way of doing >> this? > > Gilles? > > -Brad > -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
