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: R.U.10 (erudix_at_[hidden])
Date: 2008-10-13 05:43:49

2008/10/13 Vladimir Prus <ghost_at_[hidden]>

> 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.
>
(...)

> >
> > http://msdn.microsoft.com/en-us/library/aa375674(VS.85).aspx<http://msdn.microsoft.com/en-us/library/aa375674%28VS.85%29.aspx>
> <http://msdn.microsoft.com/en-us/library/aa375674%28VS.85%29.aspx>
> > http://www.codeproject.com/KB/cpp/PrivateAssemblyProjects.aspx
>
(...)

>
> 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.

That's right.

Will it be actually
> acceptable for you to edit each manifest file for each Boost library?

Yes it will be.

> Or there's
> some smarter solution that's possible?

The craftiness consists in not indicating the "publicKeyToken" info in the
manifest file generated at the time of the compilation, as it's explained in
the codeproject link above. Unfortunately the automated generation of
personalized manifest files does not work perfectly with the VC compiler. It
is all the same necessary to edit them. So, have the possibility with bjam
of not to embed the manifest into the DLL (without other intervention) would
be really useful at first. On the other hand if the manifest file is not any
more embedded, it must be next to the DLL in the default Boost\lib.

R.U.10