Question about the VC project/workspace structure

[Steve Cheng <sc...@macrovision.com>]

The AxisClient project in the Distribution workspace consists of source
coming from the different subdirectories of $AXIS_HOME/src (i.e., soap,
transport, common, etc ...).

Each of these subdirectories is already being built by a separate
project aggregated by the AxisDevelopment workspace (i.e., there is a
SOAPLibrary, AxisTransportLibrary, and CommonLibrary project for the
above).


A couple questions:

Why does the AxisClient project include the source code for the above
projects in its own project?  In other words, why isn't the AxisClient
project simply linking the static libraries generated by SOAPLibrary,
AxisTransportLibrary, etc ... to produce its DLL.


Why are SOAPLibrary, AxisTransportLibrary, etc ... built as static
libraries?  Could the Axis-C project team consider generating
shared/dynamic libraries instead of static ones in a future release?


Thanks,
Steve

RE: Question about the VC project/workspace structure

[Susantha Kumara <su...@opensource.lk>]

The AxisDevelopment workspace is not supposed to be compiled and used to
build Axis runtime now. The Distribution workspace contain all projects
that you need to build Axis (client, server, parsers, transports all).
All projects in Distribution workspace make dynamic libraries.

Actually AxisDevelopment workspace should be changed to contain
non-compilable utility projects. The purpose of it is to provide a way
to see a well categorized sections of whole code.

---
Susantha Kumara
Virtusa (pvt) Ltd.
Office : +94112714385
Mobile : +94777420453

> -----Original Message-----
> From: Steve Cheng [mailto:scheng@macrovision.com]
> Sent: Friday, May 21, 2004 7:31 AM
> To: axis-c-dev@ws.apache.org
> Subject: Question about the VC project/workspace structure
> 
> 
> The AxisClient project in the Distribution workspace consists of
source
> coming from the different subdirectories of $AXIS_HOME/src (i.e.,
soap,
> transport, common, etc ...).
> 
> Each of these subdirectories is already being built by a separate
> project aggregated by the AxisDevelopment workspace (i.e., there is a
> SOAPLibrary, AxisTransportLibrary, and CommonLibrary project for the
> above).
> 
> 
> A couple questions:
> 
> Why does the AxisClient project include the source code for the above
> projects in its own project?  In other words, why isn't the AxisClient
> project simply linking the static libraries generated by SOAPLibrary,
> AxisTransportLibrary, etc ... to produce its DLL.
> 
> 
> Why are SOAPLibrary, AxisTransportLibrary, etc ... built as static
> libraries?  Could the Axis-C project team consider generating
> shared/dynamic libraries instead of static ones in a future release?
> 
> 
> Thanks,
> Steve