axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samisa Abeysinghe" <>
Subject RE:
Date Mon, 14 Jun 2004 02:12:04 GMT
I think making the configure select the required parser and transport is
important with the configure script.
With the new design of Axis C++, user may want to build a particular
parser and not the other when given a choice.
It is no harm building make for all. However, in a real scenario, the
configure phase should validate that the required elements for the user
selection on the machine the build takes place. (Existence of headers
and libs). If we are to get there, we have to make sure that only the
required make files are generated. Else the user may have to make sure
that all the elements required by all options are available on the
machine, which is not feasible.
(E.g. If I want to use only the Xerces parser, I would not want to have
Expat on my systems. Additionally, I would like to see if configure
could pick up the headers and libs from my Xerces installation. So that
I do not have the trouble of manually copying them here and there)


-----Original Message-----
From: Sanjiva Weerawarana [] 
Sent: Friday, June 11, 2004 8:39 PM
To: Apache AXIS C Developers List
Subject: Re:

Hi Damitha,

> In other cases they are there, so that beginning from that place
> can be generated seperately. For example you can goto samples/server
> generate configure file there to create all the Makefiles beginning
> that folder.

Is it absolutely necessary to have that level of flexibility in the
build system? That is, even if someone wants to build only the server
dir, is it harmful to require them to build the makefiles for all
the dirs, then cd to the server dir and make in there? Maybe there
are scenarios I don't know about ..

I'd prefer to if there was one configure file - that will make it
easier to port to multiple platforms and also simpler for a new
user/developer to understand.


This message, including any attachments, contains confidential information intended for a
specific individual and purpose, and is intended for the addressee only.  Any unauthorized
disclosure, use, dissemination, copying, or distribution of this message or any of its attachments
or the information contained in this e-mail, or the taking of any action based on it, is strictly
prohibited.  If you are not the intended recipient, please notify the sender immediately by
return e-mail and delete this message. 

View raw message