Simplifying backend compilation on Unix/Linux

16 Aufrufe

Direkt zur ersten ungelesenen Nachricht

Mike Fechner

ungelesen,

19.04.2011, 05:00:2319.04.11

an smartcomponent-...@googlegroups.com

Dear user of the SmartComponent Library,

we are currently preparing a number of changes in the source code to simplify the compilation of the backend on Unix and Linux systems for AppServer, WebSpeed and Batch file usage. We want to achieve that all files in the

Consultingwerk.* (without subfolders)

Consultingwerk.Exceptions.*

Consultingwerk.Framework.*

Consultingwerk.OERA.*

Consultingwerk.Util.*

packages (plus subfolders) as well as the service interface procedures in OERA\support compile on non-Windows systems without any (expected) compile error.

This requires conditional compilation because source code that is only required and intended to run on Windows (.NET Framework) will fail to compile and hence may impact customers build or deploy processes. Further the FROM ASSEMBLY option on USING statements like

USING Progress.Lang.* FROM ASSEMBLY .

will speed of compilation on Windows systems especially when using many (network) folders in the propath, but is invalid on non-Windows systems.

We will be using the preprocessor variable DotNetAccessible for this purpose. Currently the variable will be set based on the value of {&WINDOW-SYSTEM} in Consultingwerk\products.i. As Progress has announced .NET support on Windows character clients and Windows AppServer processes for OpenEdge 11 we may have to tweak the current automatic setting of this variable:

/* Compilation allowed that access .NET classes?

In 10.2B it would be sufficient to test for

"{&WINDOW-SYSTEM}". For OE11 support for .NET

on the AppServer Character client is announced.

Currently we do expect that in OE11 the test

for "{&WINDOW-SYSTEM} would not be sufficient

to know if .NET assemblies are accesible. */

&IF "{&WINDOW-SYSTEM}":U BEGINS "MS-WIN":U &THEN

&GLOBAL-DEFINE DotNetAccessible

&ENDIF

We will be moving the following files/classes to subpackages of the Consultingwerk.Windows package:

Consultingwerk.Framework.API.* -> Consultingwerk.Windows.API.*

Consultingwerk.Framework.Session.LoginForm -> Consultingwerk.Windows.Session.LoginForm

Consultingwerk.Util.Controls.* -> Consultingwerk.Windows.Util.Controls.*

Consultingwerk.Util.Forms.* -> Consultingwerk.Windows.Util.Forms.*

We will be rolling out these changes with the next release of the SmartComponent Library, expected in ~ 3 months. Customer that want to get access to this modifications upfront may contact us.

Don’t hesitate to contact us if you have questions or concerns.

Best regards,

Mike Fechner

Geschäftsführer / Director

Beschreibung: Consultingwerk Ltd.