axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adrian Dick <>
Subject Fw: cvs commit: ws-axis/c/docs antbuild-guide.html
Date Thu, 23 Sep 2004 09:04:13 GMT


I've written and committed a guide to the ant build in CVS
(ws-axis/c/docs/antbuild-guide.html ).

It is not entirely clear to me where to link this in, so it will be visible
on the axis C web pages.

Adrian Dick (
WebSphere MQ and ESB Development
Tel: +44-(0)-1962-819212
Notes: Adrian Dick/UK/IBM@IBMGB
----- Forwarded by Adrian Dick/UK/IBM on 23-09-04 10:02 -----
             13-09-04 11:31                
                                       cvs commit: ws-axis/c/docs          

hawkeye     2004/09/13 03:31:12

  Added:       c/docs   antbuild-guide.html
  Axis C++ ANT Build Guide

  Submitted by: Adrian Dick

  Revision  Changes    Path
  1.1                  ws-axis/c/docs/antbuild-guide.html

  Index: antbuild-guide.html
  <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
  <TITLE> ANT Build Guide </TITLE>
  <META NAME="Author" CONTENT="Adrian Dick">
  <META NAME="Keywords" CONTENT="">
  <META NAME="Description" CONTENT="">

  <h1>Axis C++ ANT Build Guide</h1>
  This document provides instructions for using and extending the ANT based
build for the AXIS C++ project.</P>
  <P><A href="#prepareSystem">Preparing system</A><BR>
  <A href="#thirdPartySoftware">Getting necessary third party
  <A href="#cvsExtract">Getting a CVS checkout</A><BR>
  <A href="#propertyFiles">Property Files</A><BR>
  <A href="#runningTheBuild">Running the ANT build </A><BR>
  <A href="#addingExtraPlatform">Adding an extra platform </A></P>
  <H2><A name="prepareSystem"></A>Preparing system</H2>
  To use the ANT based build you will need to install the following:<UL>
             <LI>Apache ANT<UL>
                         <LI>Available from <A href="
                         <LI>These scripts have been developed and tested
using version 1.6.x</LI>
             <LI>Java SDK - required for running of ANT scripts, and the
compilation of WSDL2Ws tool
                         <LI>Require version 1.4+</LI>
             <LI>Ant-Contrib - provide numerous extensions to ANT,
including the
             compilation of C/C++.
                         <LI>Available from <A href="
                         <LI>Place JARs into <CODE>[ANT INSTALL
                         <LI>Require both ant-contrib and cpptasks</LI>
             <LI>Doxygen - Used for generating API documentation
                         <LI>Available from <A href="
             <LI>Compiler / Linker
                         <LI>For Windows - Microsoft Visual C++ v6</LI>
                         <LI>For Linux - gcc / g++</LI>
                         <LI>For AIX - IBM Visual Age for C++</LI>
  Before running ANT the following environment variables need to be
             <LI><CODE>ANT_HOME</CODE> - location of ant installation</LI>
             <LI><CODE>JAVA_HOME</CODE> - location of java
             <LI><CODE>PATH</CODE> - to include <CODE>[ANT_HOME]/bin</CODE>
and <CODE>[JAVA_HOME]/bin</CODE>.
                         <LI>Also ensure doxygen and compilers are
available on the system path.</LI>
  <H2><A name="thirdPartySoftware"></A>Getting necessary third party
  <P>Axis Cpp Developers can use either Xerces-c or the Expat XML Parsers
  to build the Axis Cpp.</P>
  <P><B>Expat XML Parser</B></P>

  <P>You can get expat binaries from <A

  <P><B>Xerces-C XML Parser</B></P>
  <P>You can get Xerces-C binaries from <A href="
  <H2><A name="cvsExtract"></A>Getting a cvs checkout</H2>

  <P>Visit <A href="windows/cpp/"></A> Click on
  “axis” and then on “CVS Repository” to find details on how to access the
  CVS Repository. <BR>In  short summary:<BR>
  Anyone can checkout the source code from our anonymous CVS server. To
  do so, simply use the following commands (if you are using a GUI CVS
  client, configure it appropriately): </P>

  password: anoncvs<BR>
  cvs -d checkout
  <P>The checkout of the repository will be created in the current
  in a folder named “<CODE>ws-axis</CODE>”<BR>
  The checked out folder ws-axis will be referred to as
  from this point on.</P>
  <H2><A name="propertyFiles"></A>Property Files</H2>
  <P>To aid in the portability of the ANT scripts, a number of property
files are used. The script will decide which to use based on the platform
in which it is currently running. The property files are found in
<CODE>ws-axis/c</CODE> with the following  naming convention:</P>
  <P>A number of example property files are provided for Windows, Linux,
AIX and Solaris, tt is intended that you update these files to suit your
development and buid environment. This includes location of third party
software dependencies and target packaging structure.</P>
  <H2><A name="runningTheBuild"></A>Running the ANT build</H2>
  <P>Having carried out the instructions above, the running of the ant
build is simply a matter of typing the following at a command prompt:</P>
  <P>This will carry out the following:</P>
             <LI>Build Axis C Client library</LI>
             <LI>Build Axis C Transport library</LI>
             <LI>Build Axis C XML Parser library
                         <LI>Expat, Xerces-C, etc configurable through the
property files</LI>
             <LI>Build and package WSDL2Ws tool</LI>
             <LI>Generate API Documentation</LI>
             <LI>Package artefacts into a distributable structure
                         <LI>This structure is configurable through the
property files</LI>
             <LI>Validate all artefacts have been correctly generated</LI>
  <P>To remove artefacts from a previous build use the following command:
  <H2><A name="addingExtraPlatform"></A>Adding an extra platform</H2>
  <P>The AXIS community would greatly appreciate your input, if you're
working on a platform not currently supported by the ANT scripts.<BR>Below,
are the steps required to add an additional platform;</P>
             <LI>Add platform detection to <CODE>pre-init</CODE> target,
eg:<PRE>&lt;condition property=&quot;linux&quot;&gt;
    &lt;os name=&quot;Linux&quot;/&gt;
             <LI>Update platform property within <CODE>initialize</CODE>
target, eg: <PRE>&lt;condition property=&quot;platform&quot;
    &lt;isset property=&quot;linux&quot;/&gt;
             <LI>Provide an additional property file in
<CODE>ws-axis/c</CODE> to match your platform. This uses the naming
convention <CODE>build.[<I>platform</I>].properties</CODE>, where
is as specified in step 2.</LI>
             <LI>Provide <CODE>compiler</CODE> definition for platform,
include a condition check for the correct platform, eg:  <PRE>&lt;compiler
id=&quot;Linuxgcc&quot; name=&quot;g++&quot; if=&quot;linux&quot;&gt;
    &lt;compilerarg value=&quot;-Wall&quot;/&gt;
    &lt;compilerarg value=&quot;-Wshadow&quot;/&gt;
    &lt;compilerarg value=&quot;-g&quot;/&gt;
    &lt;compilerarg value=&quot;-O2&quot;/&gt;
      &lt;define name=&quot;ENABLE_AXIS_EXCEPTION&quot;/&gt;
      &lt;define name=&quot;HAVE_CONFIG_H&quot;/&gt;
      &lt;define name=&quot;PIC&quot;/&gt;
    &lt;includepath path=&quot;${dir.include}&quot;/&gt;
  &lt;/compiler&gt;</PRE> Note: Compilers may extend one another, which can
be useful if an additional platform uses the same compiler, but maybe only
small variations in the parameters.</LI>
             <LI>Provide <CODE>linker</CODE> definition for platform,
include a condition check for the correct platform, eg: <PRE>&lt;linker
id=&quot;LinuxLinker&quot; name=&quot;g++&quot; libtool=&quot;true&quot;
    &lt;linkerarg value=&quot;-g&quot;/&gt;
    &lt;libset libs=&quot;stdc++&quot;/&gt;
  &lt;/linker&gt;</PRE> Note: As for compilers, linkers may extend one
             <LI>Add new <CODE>compiler</CODE> and <CODE>linker</CODE>
the <CODE>cc</CODE> task within <CODE>compileAxisClient</CODE>,
<CODE>compileAxisTransport</CODE> and <CODE>compileAxisXMLParser</CODE>
targets, eg: <PRE>&lt;cc
   exceptions=&quot;true&quot; failonerror=&quot;false&quot;
outtype=&quot;shared&quot; multithreaded=&quot;true&quot;&gt;
    &lt;!-- Compilers --&gt;
    &lt;compiler refid=&quot;Linuxgcc&quot;/&gt;
    &lt;compiler refid=&quot;AIXxlc&quot;/&gt;
    &lt;compiler extends=&quot;VisualC++&quot;&gt;
        &lt;define name=&quot;AXISTRANSPORTDLL_EXPORTS&quot;/&gt;
    &lt;!-- Linkers --&gt;
    &lt;linker refid=&quot;LinuxLinker&quot;/&gt;
    &lt;linker refid=&quot;AIXLinker&quot;/&gt;
    &lt;linker extends=&quot;VisualC++Linker&quot;&gt;
      &lt;syslibset libs=&quot;wsock32&quot;/&gt;
    &lt;!-- Files to compile --&gt;
    &lt;fileset dir=&quot;${dir.src}&quot;&gt;
      &lt;include name=&quot;transport/axis/*.cpp&quot;/&gt;
      &lt;!-- The following files need to be excluded --&gt;
      &lt;exclude name=&quot;transport/axis/SecureChannel.cpp&quot;/&gt;

View raw message