There is not currently any formal documentation for the components within OG-Language as they may be subject to change until we have finalised the release of our R integration component which depends on this library. As part of the 1.0.0 release an overview of Service, ServiceRunner, Connector and Util will be available on our docs site along with the generated C++ documentation.
To build OG-Language within a Linux environment, the log4cxx and apr components can be obtained from the Apache website or through your operating system’s package manager (e.g. yum on a Fedora system) and the Fudge library can be built using a source download from github (Vrai/Fudge-C). We are currently in the process of updating the RPM and source tarballs available on the fudgemsg.org website for this library to 0.3 (http://jira.fudgemsg.org/browse/FRC-12) as I have had reports of the 0.2 RPM not containing all of the functionality required.
Building OG-Language from a Windows environment with Visual Studio should use pre-built i386 or x64 binaries available from the OpenGamma ivy repository. If ant fails at the resolve stage on Windows, please can you post the output so that we can remedy this. To build from within Visual Studio, you will need to run a command line build first to unpack the ivy artifacts into local include and lib folders.
If these libraries are available and the project does not build, please can you post the full output from the “ant publish-local” command in the OG-Language directory so that we may investigate and correct any issues.
As Jim says, we have not yet released any components that depend on OG-Language so the failure messages caused by missing libraries should not prevent you building and testing the OpenGamma platform. If the build does not complete because of these missing libraries, please can you post the output from an “ant publish-all-local” from the OG-Platform directory so that we may correct this.