Experiments with today's git master branch are inconclusive at this point. There's something causing errors with my tree that don't occur with 2.8.12.2, but it did generate the cvproj file and, in spite of the restructuring of the vcproj generation, it looks like the GenerateManifest value is still true. I just wish I could have actually gotten the build to generate the associated executable so I could have confirmed this more strongly by examining the embedded manifest.
So I'm expecting this is still a problem, but I'm not sure. I'll do some more experimentation and update this with anything I find. On Fri, May 2, 2014 at 11:47 AM, Eric Berge <[email protected]> wrote: > Note that this was based on 2.8.12.2 but looking at the more recent code I > think there's a possibility that a fix for this "fell out" of a > restructuring of the generation of the vcproj files. I'm going to try to > build this and see if the problem appears to be fixed. > > > > > On Fri, May 2, 2014 at 10:59 AM, Eric Berge <[email protected]> wrote: > >> >> I am updating our cmake files from Visual Studio 2008 to 2012 and the >> setting of CMAKE_EXE_LINKER_FLAGS to include /MANIFESTUAC:NO (which worked >> with VS2008) appears to be ignored. The resulting exe files have the >> following manifest in them: >> >> <?xml version='1.0' encoding='UTF-8' standalone='yes'?> >> <assembly xmlns='urn:schemas-microsoft-com:asm.v1' manifestVersion='1.0'> >> <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3"> >> <security> >> <requestedPrivileges> >> <requestedExecutionLevel level='asInvoker' uiAccess='false' /> >> </requestedPrivileges> >> </security> >> </trustInfo> >> </assembly> >> >> I'm not sure, but I believe this is due to the following being included >> for the RelWithDebInfo build I'm doing: >> >> <GenerateManifest >> Condition="'$(Configuration)|$(Platform)'=='RelWithDebInfo|x64'">true</GenerateManifest> >> >> and I expect this should be "false" (but I'm not sure whether there are >> other parts of the Visual Studio project file that need to be updated as >> well. >> >> I believe this is another manifestation or is at least related to issue >> 12963 - http://public.kitware.com/Bug/view.php?id=12963 >> >> So I'm probably requesting that issue be bumped from "backlog" status. >> >> Eric >> >> >
-- 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://www.cmake.org/mailman/listinfo/cmake
