David,
It installed fine for me and seems to work fine:
C:\work.ooRexxooRexx420_0-x86_64.exe
C:\work.ooRexxrexx -v
Open Object Rexx Version 4.2.0
Build date: Sep 17 2013
Addressing Mode: 64
Copyright (c) IBM Corporation 1995, 2004.
Copyright (c) RexxLA 2005-2013.
All Rights Reserved.
This
All -
I am now able to build ooRexx using an automated script on Win7 64 bit
consistently. I still have a few tweaks to do but I should be able to
put this virtual machine into production in the next few days.
I will follow up with a 32 bit Win7 VM as soon as I can. It should not
be near as hard
Excellent!!
--
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
All -
I finally have the nightly build scripts working the way I envisioned
them! Unnecessary builds are being skipped as expected and builds are
being performed as expected.
The status subdirectory is you main key to the build process. The status
file will let you know if a build was
On Fri, Jun 25, 2010 at 7:08 AM, David Ashley
david.ashley@gmail.com wrote:
I finally have the nightly build scripts working the way I envisioned
them! Unnecessary builds are being skipped as expected and builds are
being performed as expected.
I poked around a little on the build
