It seem that the flag you're suggesting allows you to specify data for the 'dependency' element. I nee to specify the 'supportedOS' element... (Preferably still allowing the compiler to generate the manifest on my behalf, though it is acceptable to me to write the manifest by hand and then feed it to the linker somehow and have it embeded into my application -- it must be embedded though, I can't have it as a separate file).

On Wed, Mar 28, 2012 at 2:49 AM, Matthew Chambers <matt.chambers42@gmail.com> wrote:

Hi Joshua,

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.

-Matt

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

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build