This is mostly to get this question recorded for Mark for when he gets back
from vacation.
I'm currently running into some issues with the manifest file we're
embedding in rexx.exe via an include within rexx.rc. Building this via
this method causes a duplicate resource error because the cmake build tools
generate a default manifest which gets embedded via the /MANIFEST and
/MANIFESTFILE linker options. When the .rc file pulls in the second
manifest, this creates the error.
For now, I've commented out the link in rexx.rc that pulls in the manifest
file, so the cmake build is using the one it generates. For the existing
build, I've switched to rexx.mak file to use /MANIFEST and /MANIFESTFILE
link options. We're going to run into this same issue with the oodialog
executables when we get that portion working in cmake as well. I really
don't understand the manifests and what information needs to be in there.
The cmake-generated manifests and the ones we are using are quite
different. Here is our version:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity
version="1.0.0.0"
processorArchitecture="amd64"
name="RexxLA.ooRexx.rexx"
type="win32"
/>
<description>Open Object Rexx Interpreter.</description>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="amd64"
publicKeyToken="6595b64144ccf1df"
language="*"
/>
</dependentAssembly>
</dependency>
</assembly>
and here is the cmake version:
<?xml version='1.0' encoding='UTF-8' standalone='yes'?>
<assembly xmlns='urn:schemas-microsoft-com:asm.v1' manifestVersion='1.0'>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel level='asInvoker' uiAccess='false' />
</requestedPrivileges>
</security>
</trustInfo>
</assembly>
Note that cmake generates one of these for all of the dlls and exes.
So, do we need to continue using our manifest version or can just
allow the cmake defaults? Does the cmake version cause any problems
with the other files? I've found information on how to use custom
manifests, which involves disabling the automatic generation and then
adding a post-processing step that uses a tool to add the custom
manifest. A bit of a pain, but doable. I think I'd prefer to let
cmake do the heavy lifting if we can.
Rick
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
