OpenEdge .r files are much like Java class files: They are platform-independent byte codes that gets executed on a virtual machine.
For Java this would be the java.exe, for OpenEdge it would be the
- prowin32.exe ( GUI Windows 32Bit ),
- prowin.exe ( GUI Windows 64Bit ),
- _progres.exe ( CHUI Windows, batch )
- or _progres ( *nix ).
Therefore you don't build an executable - you invoke the virtual machine with the corresponding paramter -p ( lower case - parameters are Unix-style ) and the path to the .r file.
Usually you would do this in shell script or on Windows with a shortcut.
Heavy Regards, RealHeavyDude.