Great stuff! We should add this to the wiki/website.

On 19/07/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:

I just finished setting up a Tuscany C++ development and build
environment on my Linux machine and thought it would be useful to share
the steps I went through.

I am using Redhat Linux Enterprise 4, but the same steps should work on
other Linux systems like Fedora Core or Ubuntu for example.
These steps take no more than 15 mns to complete, starting from scratch.
After you complete them you should be all set to build the Tuscany C++
runtime, and start contributing :)

From a shell prompt, create a $HOME/tuscany directory.

Install the following prerequisites:

* Subversion - SVN version 1.3.0 or later is good (most Linux distros
already include SVN).

* Ant and a Java JDK are required by the SCA code generation tool used
to generate proxies and wrappers for C++ components.
Download apache-ant-1.6.5-bin.tar.gz from
http://ant.apache.org/bindownload.cgi.
From $HOME/tuscany do tar xzf apache-ant-1.6.5-bin.tar.gz.
Configure your environment:
export ANT_HOME=$HOME/tuscany/apache-ant-1.6.5
PATH=$ANT_HOME/bin:$PATH

Download jdk-1_5_0_06-linux-i586.bin from
http://java.sun.com/j2se/1.5.0/download.jsp.
From $HOME/tuscany run jdk-1_5_0_06-linux-i586.bin, this will extract
the JDK in $HOME/tuscany/jdk1.5.0_06.
Configure your environment:
export JAVA_HOME=$HOME/tuscany/jdk1.5.0_06
PATH=$JAVA_HOME/bin:$PATH

* Libxml2 2.6.20 or later
Libxml2 is already in most Linux distros, just check that you have
version 2.6.20 or later (my RHEL4 system had an older version and I had
to upgrade it).
To see which version of libxml2 is installed on your system do rpm -aq |
grep libxml2.
Configure your environment:
export LIBXML2_LIB=/usr/lib
export LIBXML2_INCLUDE=/usr/include/libxml2

* Axis2C version 0.92
Download axis2c-bin-0.92-linux.tar.gz from http://ws.apache.org/axis2/c.
From $HOME/Tuscany do tar xzf axis2c-bin-0.92-linux.tar.gz, this will
install Axis2C in $HOME/Tuscany/axis2c-bin-0.92-linux.
Configure your environment:
export AXIS2C_HOME=$HOME/tuscany/axis2c-bin-0.92-linux
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$AXIS2C_HOME/lib


Download the Tuscany C++ code:
From $HOME/tuscany, do svn co
http://svn.apache.org/repos/asf/incubator/tuscany/cpp, this will check
out all the source code in $HOME/tuscany/cpp.

Configure your environment:
export TUSCANY_SCACPP=$HOME/tuscany/cpp/sca/deploy
export TUSCANY_SDOCPP=$HOME/tuscany/cpp/sdo/deploy
export
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$TUSCANY_SDOCPP/lib:$TUSCANY_SCACPP/lib

The builds use the GNU automake + configure tools, which nicely analyze
your environment and generate all the make files you need.

To build the SDO C++ runtime:
cd $HOME/tuscany/cpp/sdo
./autogen.sh
./configure --prefix=$TUSCANY_SDOCPP --enable-static=no
make
make install
cd $HOME/tuscany/cpp/sdo/samples
./autogen.sh
./configure --prefix=$TUSCANY_SDOCPP --enable-static=no
make
make install

Note: Tuscany already has build.sh scripts that do all of this for you,
but I wanted to use the individual commands to understand what was going
on at each step.
Also, when you make code changes in general you just run make and make
install and not the whole set of steps.

To run the the SDO test suite:
cd $HOME/tuscany/cpp/sdo
./sdotest.sh

To build the SCA C++ runtime:
cd $HOME/tuscany/cpp/sca
./autogen.sh
./configure --prefix=$TUSCANY_SCACPP --enable-static=no
make
make install
cd $HOME/tuscany/cpp/sdo/samples
./autogen.sh
./configure --prefix=$TUSCANY_SCACPP --enable-static=no
make
make install

To run the SCA runtime tests:
cd $HOME/tuscany/cpp/sdo
./scatest.sh

To run the SCA calculator sample:
cd $HOME/tuscany/cpp/sca/deploy/samples/Calculator/deploy/bin
./runclient.sh

Overall it was pretty simple. I hope these steps will help people set
their C++ build environment and come help us!

Could other people in the group try these steps in other environments
and see if they work for them?
Do we have similar steps for Windows?

--
Jean-Sebastien


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Pete

Reply via email to