axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Cheng" <sch...@macrovision.com>
Subject Question about the VC project/workspace structure
Date Fri, 21 May 2004 01:31:28 GMT


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


Mime
View raw message