I am a bit late to the thread but I also had this problem so I made it a
"policy" NOT to install the VS update that broke the Manifest thing. Easy for
me as I am a single guy shop :-) but it did get rid of the problem, or more
correctly worked around the problem. Of course the downside is that I
On Tue, May 3, 2011 at 12:17 PM, Bill Hoffman wrote:
> My blog entry might help:
>
> http://www.kitware.com/blog/home/post/4
Thanks, Bill. That's a good summary of the issues. It would have been
really useful to me a few days ago :), but hopefully this saves
someone else some time. The tip about
On 5/3/2011 11:52 AM, Tyler wrote:
Yes, I verified the manifests in each binary with strings + grep.
Everything is produced with a version of 9.0.21022.
My blog entry might help:
http://www.kitware.com/blog/home/post/4
-Bill
___
Powered by www.kitw
Yes, I verified the manifests in each binary with strings + grep.
Everything is produced with a version of 9.0.21022.
tyler
On Tue, May 3, 2011 at 8:49 AM, John Drescher wrote:
> On Tue, May 3, 2011 at 11:43 AM, Tyler wrote:
>> My project makes use of the CMake/CPack module
>> InstallRequiredSy
On Tue, May 3, 2011 at 11:43 AM, Tyler wrote:
> My project makes use of the CMake/CPack module
> InstallRequiredSystemLibraries to package Microsoft Visual C Runtime
> libraries with other build artifacts. Despite this and despite the
> presence of appropriate-looking files showing up in the insta
My project makes use of the CMake/CPack module
InstallRequiredSystemLibraries to package Microsoft Visual C Runtime
libraries with other build artifacts. Despite this and despite the
presence of appropriate-looking files showing up in the installed
image, my project does not run on XP and Vista mac
