Subject: Re: [Boost-build] MSVC Manifest Files
From: Matthew Chambers (matt.chambers42_at_[hidden])
Date: 2012-03-27 11:49:31
Have you tried the MANIFESTDEPENDENCY flag? It's like:
/MANIFESTDEPENDENCY:\"type='win32' name='<manifest-filename>' version='<assembly version>'\"
Note that if you intend to support Windows XP, the name of the manifest can not match the basename
of the DLL because of a Windows XP loader bug.
On 3/22/2012 6:54 AM, Joshua Boyce wrote:
> Hello all,
> Using Boost.Build, how do I specify a manifest file to use for my binary (which should then be
> embedded into my application)? Specifically, I want to add the "supportedOS" info to my
> application's manifest. I previously needed to add UAC compatibility to my manifest, but I worked
> around that with the MANIFESTUAC linker flag, and the auto-generation continued to suffice, but
> there is no equivalent linker flag for the supportedOS manifest data, so I need to be able to
> specify a manifest file on-disk.
> I'm spoiled by Visual Studio as it handles this all for you in a few clicks. I can't figure out how
> to do it with Boost.Build (I've scoured the docs but to no avail).
> Thanks in advance.
> Unsubscribe& other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk