On Wed, May 21, 2014 at 2:39 PM, Rick McGuire wrote:
> Yep, I caught that. I had also added it to rexxc.exe because I didn't
> understand what it was for. That one can be removed.
>
> Btw, I see ooDialog has a .exe file and a .com file. I think I've got
> those building correctly, but I'm not
Yep, I caught that. I had also added it to rexxc.exe because I didn't
understand what it was for. That one can be removed.
Btw, I see ooDialog has a .exe file and a .com file. I think I've got
those building correctly, but I'm not sure I understand what the .com file
is for. I'm also adding th
On Wed, May 21, 2014 at 2:29 PM, Rick McGuire wrote:
> Mark,
>
> Thanks for the answer. I did find a solution for this. It turns out to
> possible to replace or merge additional manifest information into the
> executables as a post-processing step. I wasn't really sure which .exe
> files neede
Mark,
Thanks for the answer. I did find a solution for this. It turns out to
possible to replace or merge additional manifest information into the
executables as a post-processing step. I wasn't really sure which .exe
files needed this, so I end up merging it into them all. If only ooDialog
ne
Hi Rick,
I'm still traveling and only have good Internet once in awhile. So I've
put off answering this. But thought I'd better do something about it.
The existing manifest was only needed for ooDialog. The important part is
the part to load the 6.0 common controls library:
Open Object Rexx
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 bui
