From: Mark Miesfeld <miesfeld@gm...> - 2010-08-19 16:02:28
This is only of concern if you plan on running the packaging step of
the Windows build:
Download: ooRexx-build-utils-1.2.0-windows.zip from SourceForge. Its
under oorexx-buildutils. Unpack it.
Put ooRexxProcess.dll in the Plugins directory of your NSIS installation
Replace your existing killer.exe with the one from
On Windows we use NSIS to create the installation package. NSIS
supports 'plugins' and oorexx.nsi uses a number of plugins for various
tasks. None of the existing plugins I've looked at do a good job of
determining if rxapi is running and / or killing it.
So, I wrote our own plugin. ooRexxProcess.dll
Source code is in:
I put a new release of oorexx-buildutils up on SourceForge that has
the prebuilt ooRexxProcess.dll in it.
ooRexx-build-utils-1.2.0-windows.exe (self-extracting zip file.)
I have changes to oorexx.nsi that, once I commit, will require
ooRexxProcess.dll to package ooRexx.
It is simply a matter of putting ooRexxProcess.dll in the Plugins
directory of your NSIS installation:
Directory of C:\tools\NSIS\Plugins
08/18/2010 02:29 PM 4,096 ooRexxProcess.dll
When I rebuilt killer.exe, it started working again on my system.
Without any code changes, I just rebuilt it. On the system where it
stopped working for me, I had moved up to Visual Studio 2008. It's
probably some stupid library thing.
It may be that it needs to be statically linked to the libraries ...
not really sure.
If for some reason either killer or the ooRexxProcess plugin do not
work on the build machine, I think just building from source will fix
it for you.
svn co https://oorexx.svn.sourceforge.net/svnroot/oorexx/build-utilities/trunk
edit Nmake.inc - Put in the directory path to your NSIS installation
NSIS_API_DIR = C:\Tools\NSIS
nMake /F Makefile.win <- builds killer
nMake /F Makefile.win ooRexxProcess_Plugin <- builds ooRexxProcess.dll
ooRexxProcess.dll is not in the 'all' build because it requires NSIS
to be installed.