Answered Compile Progress OpenEdge 12 CHUI/SpeedScript within Linux

S

sir_elevated_privileges

New Member
Hello guys,

I am migrating from a full Linux (Rocky/RHEL 9.x) stack with Progress OpenEdge 11.7.x to Progress OpenEdge 12.8. This includes Apache Ant routines and a lot of ancient structured code made exclusively for Linux. The main idea is to move all this to a modern architecture and work with ABL OOP, but in the meanwhile I want to compile all the .w programs with the ABL compiler (such as a .p ABL program) into the new version with its respective compatibility handler (such as this doc says: docs.progress.com/bundle/openedge-migrate-classic-appserver/page/Migrate-Classic-WebSpeed-Applications.html but within Linux instead of Windows PDSOE, for environmental reasons).

So, I have this partner who says "In Progress OpenEdge 12, they obligates you to compile only through the PDSOE, and you cannot compile in Linux anymore." refusing to give me a compilation license for Linux installation. But in the Progress OpenEdge installation directory I find compiling stuff like "_comp.r" and more...

My question is: Is that true? I find out that compiling for PASOE does obligates me to use the PDSOE but everything else too? This implies I have to modify all my workflows and all my pipelines, and also my git repo because I have different build.xml in some directories which connects with different databases to compile some parts of the code (like different projects inside PDSOE). And that does not ends here, a lot of libraries crash when I want to mention the tutorial in the mentioned doc page.

DISCLAIMER: I didn't link and I did remove the protocol of the URL because the platform says it is spam or suspicious.
 
Sorry about the auto-mod of the post. We've dialled it in quite tightly recently due to an influx of spambots and yours didn't make the cut. I've approved now.

As to your question, you can definitely compile on Linux. Whilst we don't do Speedscript or CHUI, we do classic webspeed and that's always been compiled on our Linux box.
 
You are not obligated to use PDSOE to compile. That’s nonsense. Someone has misunderstood something.

Progress sells compiler licenses for Linux. So, clearly, it is possible.

There are certain things that you sort of, maybe, might, need PDSOE for in development, like generating PAAR files, but that has nothing to do with compiling per se. (And if you’re clever you can likely work out how to get around that.)
 
TomBascom said:
There are certain things that you sort of, maybe, might, need PDSOE for in development, like generating PAAR files, but that has nothing to do with compiling per se. (And if you’re clever you can likely work out how to get around that.)
Click to expand...

It's less "clever" and more "enjoys suffering" :D
 
Thank you for your response! It's much of what I search. I'm glad you also hate PDSOE.

Just a final clarification: So even to compile PASOE source code it is not necessary the PDSOE. And which utility do you use if so?
 
Last edited:
sir_elevated_privileges said:
Thank you for your response! It's much of what I search. I'm glad you also hate PDSOE.

Just a final clarification: So even to compile PASOE source code it is not necessary the PDSOE. And which utility do you use if so?
Click to expand...
PASOE source code is just ABL source code. No need for anything special to compile it.

What you DO need PDSOE for, is for creating certain kinds of service artifacts (eg REST API).
 
You must log in or register to reply here.
Back
Top