[prev in list] [next in list] [prev in thread] [next in thread] 

List:       axis-c-dev
Subject:    Re: configure.ac
From:       Samisa Abeysinghe <samisa_abeysinghe () yahoo ! com>
Date:       2004-06-14 3:46:05
Message-ID: 20040614034605.45669.qmail () web40608 ! mail ! yahoo ! com
[Download RAW message or body]

Hi,
   
--- Aleksander Slominski <aslom@cs.indiana.edu> wrote:
> hi,
> 
> why there can not be just one top level cnfigure script with options like
> 
> ../configure [--with-expat=PATH] [--with-xerces=PATH] 
> [--with-apache2=PATH] [--with-apache=PATH] [--deploy-dir=PATH]

Well this is the solution required. Apparently the problem is there is lack of expertise on how
exactly this could be done.

Samisa...

> 
> after running this configure all is left for developer would be:
> make
> make deploy (which copies necessary deployment config to deploy dir)
> 
> i think that would be way simpler than current lot of steps (and three 
> bootstrap/configure scripts) and manual editing required to get anything 
> to compile ...
> 
> thanks,
> 
> alek
> 
> Samisa Abeysinghe wrote:
> 
> >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)
> >
> >Thanks,
> >Samisa...
> >
> >-----Original Message-----
> >From: Sanjiva Weerawarana [mailto:sanjiva@opensource.lk] 
> >Sent: Friday, June 11, 2004 8:39 PM
> >To: Apache AXIS C Developers List
> >Subject: Re: configure.ac
> >
> >Hi Damitha,
> >
> >  
> >
> >>In other cases they are there, so that beginning from that place
> >>    
> >>
> >Makefiles
> >  
> >
> >>can be generated seperately. For example you can goto samples/server
> >>    
> >>
> >and
> >  
> >
> >>generate configure file there to create all the Makefiles beginning
> >>    
> >>
> >from
> >  
> >
> >>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.
> >
> >Sanjiva.
> >
> >
> >
>
>--------------------------------------------------------------------------------------------------
> >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. 
> >
> >  
> >
> 
> 
> -- 
> The best way to predict the future is to invent it - Alan Kay
> 
> 



	
		
__________________________________
Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/ 
[prev in list] [next in list] [prev in thread] [next in thread]