Section 4.2: Engines Up Main page Chapter 6: Aubit4GL Compilers  

5 Modules

5.2.1 Choices

Aubit4GL uses an abstraction layer for many of its functions. This means that the way Aubit4GL works can be controlled very tightly by the setting of various variables. These variables specify which library functions will be called from the compiler and/or 4GL program and hence affect the following areas:
Variable Function Library
A4GL_LEXTYPE Set generation language libLEX_???
A4GL_LEXDIALECT Set language dialect (used for ESQL/C generation) libESQL_???
A4GL_PDFTYPE Specify the enhanced report handler libEXREPORT_???
A4GL_HELPTYPE Specify the help handler libFORM_???
A4GL_MENUTYPE Specify the extended menu handler libMENU_???
A4GL_MSGTYPE Specify the message handler libMSG_???
A4GL_PACKER ’packer’ to use saving forms/reports etc (eg. XML) libPACKER_???
A4GL_RPCTYPE Specify the Remote Procedure Call handler libRPC_???
A4GL_SQLTYPE Specify the SQL handler libSQL_???
A4GL_SQLDIALECT Specify the SQL dialect to use libSQLPARSE_???
A4GL_UI output module to use to display the program libUI_???
Aubit4GL’s libraries are created in the directory $AUBITDIR/plugins-1.2_14. With each new version of Aubit4GL a new plugins directory is created. This allows you to revert to earlier versions more easily.
Most of them have filenames of the form libXXX_YYY.so (except libaubit4gl.so) so for example :
libSQL_esql.so XXX=SQL YYY=esql
libUI_HL_TUI.so XXX=UI YYY=HL_TUI
The XXX represents the module type, the YYY the module name. Although Aubit4GL is distributed in a form which will be mostly Informix4GL compatible - you will almost certainly need to adjust some of these settings.
This is my list. Yours will probably be different! :
The correct selection of these libraries is critical to the operation of Aubit4GL, because everything is so highly configurable.
 Section 4.2: Engines Up Main page Chapter 6: Aubit4GL Compilers