Re: [Boost-build] [BBv2] [msvc] Embedding a manifest intoanexecutable does not work as expected.

From: Johan Nilsson (r.johan.nilsson_at_[hidden])
Date: 2005-11-30 02:41:46

"Johan Nilsson" <r.johan.nilsson_at_[hidden]> wrote in message 
news:dmhiaq$3km$1_at_sea.gmane.org...
>
> "Vladimir Prus" <ghost_at_[hidden]> wrote in message
> news:200511141815.51354.ghost_at_cs.msu.su...
>> Hi Alexey,
>>
>>> Resource ID
>>> of a manifest should be 1 for an executable and 2 for dll. The attached
>>> patch fixes this issue.
>>
>> Applied, thanks!
>
> Any chance of having this applied to the RC_1_33_0 branch as well before
> Boost 1.33.1 is released?
>
> I'm currently using this version in a project of mine, and running my .exe
> files results in complaints about msvcr80(d).dll not being found.

Oops, I was too quick posting - I applied those changes manually to the 
msvc.jam in my local copy of BBv2 from RC_1_33_0 but they weren't enough be 
themselves. I also had to add the relevant changes (MANIFEST + 
RESOURCEFLAGS) to msvc.flags.

I also wondering why the regression tests for 1.33.1 were being able to run 
successfully without this, but I guess that they are run straight from the 
output directory (besides the fact that they are run using BBv1(?). I saw 
the above failure after installing the .exes (using the install rule).

BTW, wouldn't it make sense to e.g. have the foo.exe.manifest files 
installed along with the foo.exe if the manifest isn't embedded as a 
resource? Possible to implement?

Thanks // Johan