> -----Original Message----- > From: cmake-developers [mailto:cmake-developers-boun...@cmake.org] > On Behalf Of Brad King > Sent: Monday, September 14, 2015 20:16 > To: James Johnston > Cc: cmake-developers@cmake.org > Subject: Re: [cmake-developers] CMake user-provided manifest files > > On 09/11/2015 11:45 AM, James Johnston wrote: > > Because CMake already does *some* things with the linker it makes it > > impossible for me to cleanly specify and use link.exe manifest-related > > switches myself. For example, it hard-codes usage of link.exe > > /MANIFESTFILE and the user can't specify their own location. And the > > locations it does use are undocumented. > > Is there a use case for doing something with the linker-generated manifest > file other than passing it to a "mt" invocation along with (possibly) user- > specified manifest files? If not then there is no reason to make the manifest > file location public.
I can't think of anything like that. The only reason I was using the undocumented linker-generated manifest location was to merge it with my own manifest using mt.exe. So I agree, I can't think of a reason the location needs to be publicly documented/available if CMake can cleanly handle user-provided manifests to merge. Best regards, James Johnston -- 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
