On Tue, Sep 17, 2013 at 10:13 AM, hakan <[email protected]>wrote:
> **
> In that lighting and David's case, can't rxapi kill it self when the build
> is finnished, that way David should be able to build both version on same
> VM without bother about rxapi, except for the Win32Rel directory stuff.
> If oorexx not installed, kill rxapi unconditionally. How to solve if
> oorexx is installed ? which rxapi (32 or 64) to kill and when/how, but as I
> recall if rxapi is not started it will be, maybe not as a service in these
> rare circumstances when someone building oorexx/oodialog, so kill them both
> (32/64).
> /hex
>
>
On Windows, whether it is installed as a service or not, rxapi will take
command line parameters. Try:
rxapi /?
There is no switch for it to end itself, but one could be added:
rxapi /k
Then the bitness of the system or rxapi wouldn't matter, you could just
tell it to end itself.
--
Mark Miesfeld
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
