Re: [Boost-build] Do not embed manifest in DLL for isolated application with private assemblies

Subject: Re: [Boost-build] Do not embed manifest in DLL for isolated application with private assemblies
From: Vladimir Prus (ghost_at_[hidden])
Date: 2008-10-13 03:47:49

On Wednesday 08 October 2008 12:06:02 R.U.10 wrote:
> 2008/9/25 Vladimir Prus <ghost_at_[hidden]>
> 
> > On Wednesday 24 September 2008 19:29:07 R.U.10 wrote:
> >
> > > I do not succeed in finding how to compile the boost DLL without
> > embedding
> > > manifest.
> > >
> > > I created an isolated application with private assemblies (VC80 CRT) and
> > the
> > > library boost_thread-vc80-mt-1_36.dll raises me a problem. It fetches the
> > > CRT libraries in windows\winsxs folder but I require from her that it
> > > fetches my CRT libraries into my application folder.
> >
> > Ideally, some of Windows experts should comment on this, since I know next
> > to nothing about manifests. If no such expert appears, can you:
> >
> 
> Thank you very much to consider my problem.
> 
> >
> > 1. Point me at the docs about this manifest thing
> 
> 
> http://msdn.microsoft.com/en-us/library/aa375674(VS.85).aspx<http://msdn.microsoft.com/en-us/library/aa375674%28VS.85%29.aspx>
> http://www.codeproject.com/KB/cpp/PrivateAssemblyProjects.aspx
> 
> >
> > 2. Exactly tell what you want to happen, or not happen.
> 
> 
> I need the manifest is not included into boost_thread DLL to force the use
> of the associated standalone manifest file which I modify manually.
> It's easy to do that into Visual Studio: "<Projectname> Property Pages
> Dialog Box" > "Configuration Properties" > "Manifest Tool" > "Input and
> Output" > "Embed manifest" > "No" - but I did not find such an option into
> bjam...
> 
> Perhaps I found the file which manage that in
> .\boost_1_36_0\tools\build\v2\tools\msvc.jam at line 976 but I do not really
> master what happens in this file so I hesitate to modify it for my own
> needs. I hope that someone who takes charge of bjam will want to add an
> option for this manifest embedding.

I've read a bit on this topic. IIUC, right now, the manifest file is auto-generated
used some magic, and then embedded into the DLL as resource, and you want
it to be not embedded, so that you can edit the manifest file. Will it be actually
acceptable for you to edit each manifest file for each Boost library? Or there's
some smarter solution that's possible?

Thanks,
Volodya