On Tue, Oct 29, 2013 at 12:56 PM, Staffan Tylen <staffan.tylen@gmail.com> wrote:
 
Mark, I tried running rexx.exe directly against a rexx program but it failed in the same way. Actually ooDialog.exe is not used by the app so it shouldn't have been on the list in the first place.

Long time ago I tried to compile ooRexx on my own but got so many problems that I gave up. And I haven't tried since. But maybe it's time for a new attempt. I will have a go but may need guidelines on the way as I've understood it's a different beast than the rest.

It's not really different than what you have been doing.  It just uses a .bat to drive the make, rather than a traditional make file.

If I were you, I would use the 4.1 fixes branch:

https://svn.code.sf.net/p/oorexx/code-0/main/branches/4.1/trunk

* Set up your compile environment just like you do to compile ooDialog.  

* Set 2 environment variables

set SRC_DRV=C:
set SRC_DIR=\work.ooRexx\wc\main.4.1.fixes

SRC_DRV is the drive letter.  SRC_DIR is the top-level directory of the source code tree.

* Populate the doc directory with the docs or fake files.  You only need to do this if you want to try and create the installer package.  You could just skip it and take the built binaries and use them

Then cd to the top level directory of your ooRexx source code tree and run:

makeorx NODEBUG

The windows-build.txt file is reasonably up to date.  I'd read that for details and then ask questions if you need to.

--
Mark Miesfeld