DXCommon

Ian Tree  10 May 2012 12:25:00

The DXCommon Common Code Package

Distributions for Version 3.14.1

The contents of the Windows (.zip) distribution and the Linux (.tar.gz) distribution are identical differing only in the packaging method.

Downloads

Click (once) on the icon of the file you want to download and select "Save" when asked what you want to do with the file.

Source Packages

File	File Name	Contents/Usage	File Size
Windows:
DXCommon	DXCommon-31401-109.zip	DXCommon Common Code Package Version: 3.14.1 for Windows	496 Kb
Linux:
DXCommon	DXCommon-31410-109.tar.gz	DXCommon Common Code Package Version: 3.14.1 for Linux	402 Kb

Installing the DX Common Code Package

The default Domino eXplorer development environment follows the Visual Studio paradigm of a “Solution” directory that contains multiple “Project” directories with a single application directory per application, this paradigm is followed on both Windows and Linux development environments.

Solution Directory - [any name]    Common Code Sub-Directory - "DXCommon"    Application Project Directory - [Application Name]

In Visual Studio the DXCommon project directory should have the “Do Not Build” property set.

The standard DX header and code files are NOT designed to be added to the default include search directories on either environment. The package expects to find a directory called “DXCommon” as a project level directory in each solution directory that will be used to build DX applications, these should be included in applications by relative re-direction. An include statement for the PlatBase.h header file that is located in the “Platform” sub-directory of the DXCommon package would be coded as follows.

//  Platform Includes #include        "../DXCommon/Platform/PlatBase.h"        //  Basic platform includes

Although a copy of the DXCommon package could be physically placed in each solution directory it would be more usual to place the package in a shared location on the development workstation/server and then create a symbolic link in each of the solution directories.

Windows:

The DXCommon kernel is supplied as a zipped archive (.zip). The contents of the archive should be unpacked to either the \DXCommon directory or unpacked to a directory that will then be used as the base for a symbolic link from the \DXCommon directory.
As an example.
Unpack the DXCommon kernel into a directory “c:\usr\include\DXCommon-3.14.0” and then create the symbolic link from within the solution directory using the following command.

   mklink /D DXCommon “c:\usr\include\DXcommon-3.14.0”

Linux:

The DXCommon kernel is supplied as a gzipped archive (.tar.gz). The contents of the archive should be unpacked to either the /DXCommon directory or unpacked to a directory that will then be used as the base for a symbolic link from the /DXCommon directory.
File ownership and access settings should be adjusted according to your local policies.
As an example.
Unpack the DXCommon kernel into a directory “/usr/include/DXCommon-3.14.0” and then create the symbolic link from within the solution directory using the following command.

   ln -s /usr/include/DXCommon-3.14.0 DXCommon

This deployment model allows different levels of the DXCommon package to be used in different solutions without reconfiguring the development environment.

LINKS

Information	Source Packages	Documentation	Articles
Background DX Reference Environments DX Development Environments DX Support DX Services Frequently Asked Questions License	DX Common Code QCopy QMove QACLMorph RDBCreate DXIPA DXTell SPZap	DX Application Design Guide DX Kernel API Reference DX Component Architecture DX Class Catalogue Using QCopy Using QMove Using QACLMorph Using RDBCreate Using DXIPA Using DXTell Using SPZap	Heavy Lift Computing Autonomic throughput optimisation

Share:

Tweet

• Comments [0]