On Fri, Jun 29, 2012 at 7:04 AM, Rick McGuire <[email protected]> wrote:
> I'm trying to use the API test binaries to investigate a problem, and
> just spent about 30 minutes banging my head against the wall trying to
> figure out why the API dlls won't load until I realized I was trying
> to load the old 32-bit version using the 64-bit interpreter. So, a
> couple of questions:
>
> 1) Can you refresh my memory on how to force the APIs to rebuild, and
> 2) Are there any special considerations for getting these to rebuild
> as 64-bit executables?
>
>
Rick,
Use capital B (-B) to force the binaries to rebuild:
testOORexx.rex -B
You can add -n to just build the binaries and not run any tests:
testOORexx.rex -B -n
ooTest Framework - Automated Test of the ooRexx Interpreter
Interpreter: REXX-ooRexx_4.2.0(MT) 6.04 27 Jun 2012
Addressing Mode: 64
ooRexxUnit: 2.0.0_3.2.0 ooTest: 1.0.0_4.0.0
Tests ran: 0
Assertions: 0
Failures: 0
Errors: 0
Skipped files: 0
Total time: 00:00:11.404000
There shouldn't be anything special that needs to be done to build the
64-bit version. Whether the compiler / linker builds 64-bit versions is
dependent on the the options passed to vcvarsall.bat, or setEnv.cmd if
setting up through the SDK.
So, if you have things set correctly to build the interpreter with 64-bit,
then you shouldn't need anything different to build the API tests.
--
Mark Miesfeld
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
