[omniORB] question(s) regarding omniORB-4.1.1 and VisualStudio2005 (VS2005) manifest files

[Duncan Grisby]

On Tuesday 1 January, Nikola Radovanovic wrote:

> I saw that omniORB-4.1.1 delivers manifest linked to its executables
> (ie omninames) as a resource, which is OK, but checking given exe
> (with resource hacker tool) - one will see that parameter for mt.exe
> is wrong (it should be 1, but it is 2), regarding MS specification
> which can be found on
> http://msdn2.microsoft.com/en-us/library/ms235591.aspx.
> Also i have noticed that manifests for shared libraries are generated
> by compiler, but neither one dll has linked manifest as a resource.
> I would like to know if this 'manifest things' are done deliberately
> (and if so-why)?

I wonder why it works when it has the wrong option?  I've applied your
changes in CVS.

By the way, your patch was backwards. It didn't really matter since it
was easy to apply by hand, but for anything more complex, make sure you
do the diff the right way around.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --