How to check if r-code compiled for webspeed

J

jfsampa

New Member
Hello,

We use WebSpeed and we compile in workshop.
And we also use Client Applications and AppServer in Windows and Linux and we use prowin32 compilation.

Is there any way to know if a r-code ".r" file was compiled in workshop or in prowin32 ?

Any idea ?

Thank you very much and very nice site and forums.

JoseF
 
The easiest way is to split things up into multiple directories, for example:

- client
- shared
- server

And then compile everything in the client directory tree with prowin32.exe and everything in the shared and server trees with _progres.exe - your same server r-code set should then also work for both windows and linux.

Since we have quite some legacy before evolving into our current n-tier model, we could not make a strict split up like above and therfore use the following compile rules with our custom compiler:

1. compile all sources with _progres.exe and package this in a server.pl
2. compile all sources that had a compile error containing the error 'ForceErrorInChui' with prowin32.exe
3. package all r-code that was compiled with prowin32.exe + all r-code that has a name ending in -c.r + all r-code in a hard-coded list since its also required on the client in the client.pl

The compiler error is simply forced into the source by beginning the source with something like:

&IF SESSION-DISPLAY-TYPE <> "GUI" &THEN
ForceErrorInChui
&ENDIF
 
Stefan,

Thank you for your kind and quick answer.
Many good ideas.

My problem right now is that I have an r-code file (actually from a third party) that I need to verify if it was compiled in prowin32 or in workshop.

How do I know how an specific r-code file was compiled ?

Any idea ?

Thank you again,

JoseF
 
Assuming you are not on an ancient version of Progress OpenEdge:

Code: 
RUN wrong.r.
 
CATCH e AS progress.lang.proerror:
   IF e:GetMessageNum(1) = 4438 THEN
      MESSAGE 'oops' VIEW-AS ALERT-BOX.
END CATCH.
 
You must log in or register to reply here.
Back
Top