On Wed, May 21, 2014 at 2:39 PM, Rick McGuire <object.r...@gmail.com> 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 sure I understand what the .com file
> is for. I'm also adding the manifest to that one.
>
The .com file is essentially to allow:
C:\work.ooRexx>oodialog -v
ooDialog 4.2.4.10010
C:\work.ooRexx>
The .com file runs first and parses the command line. If the command line
indicates a GUI application is needed, it restarts itself as oodialog.exe.
oodialog.exe is linked as subsystem:windows, while oodialog.com is linked
as subsystem:Console
So, I don't think oodialog.com needs the manifest, but I don't remember for
sure. It would depend on if oodialog.exe is started as a separate process
or created as a child process. Which I don't remember off the top of my
head.
--
Mark Miesfeld
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel