You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by John Hawkins <HA...@uk.ibm.com> on 2004/06/10 17:49:12 UTC

configure.ac




Hi Folks,

Trying to get the latest code building on AIX.

The compiler I'm using is not understanding the CPPFlags but I know what to
set them to. My question is - if I change configure.ac in the c directory
why are there other configure.ac's in other directories (listed below) ->

/home/hawkeye/axis12
# find . -name configure.ac -print
./configure.ac
./samples/client/configure.ac
./samples/client/testHandler/configure.ac
./samples/server/configure.ac
./samples/server/echoStringHeaderHandler/configure.ac
./samples/server/interoptests/doclitbase/configure.ac
./samples/server/interoptests/doclitgroupB/configure.ac
./src/server/handlers/global/testhandler1/configure.ac
./src/server/handlers/transport/testhandler2/configure.ac
./src/wcg/configure.ac
./src/xml/txpp/lib/configure.ac
./tests/configure.ac

I think what's happening is that when I run build.sh, configure is picking
up the configure.ac files in the different directories. I don't want to
change the configure.ac files for all these directories everytime I want to
build on a new platform so, what can we do? Why do we have all these
configure.ac files ?  Why not just have the one root configure.ac file that
holds the flags for that platform?

thanks for any help (Ignorance plays a large part in my questions so bare
with me :-)

John Hawkins


Re: configure.ac

Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
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.


Re: configure.ac

Posted by Kenneth Chiu <ch...@cs.indiana.edu>.
John, re-reading my response, I see that it wasn't very
clear.  I was actually agreeing with you.  I also do not
understand why there are so many configure.ac files.  But I
was trying to say that _if_ there really is a need for
multiple configure.ac files, I suggest that Axis do things
the usual autoconf way, which is to have one place for the
additional macros or include file.  You add your AIX stuff
to this one place.  All configure.ac files will refer to
this one place.

So if you cannot convince people to eliminate the extra
configure.ac files, you can at least ameliorate the
situation somewhat.

On Fri, 11 Jun 2004, John Hawkins wrote:

>
>
>
>
> Hi Kenneth,
>
> I appreciate that the end-user has no issues with this -  I'm coming from
> the viewpoint of having to compile Axis C on X different platforms (where
> X> 5 let's put it that way). Therefore I don't want to make 8*5 changes
> (plus any other things I have to do) on every platform . I thought the
> point of libtools was that they encapsulated platform specific issues into
> their structure?
>
> My points still hold about the fact that we have 8 configure files for a
> not very big project. When, in my humble opinion, we could either have one
> (src)or a maximum of three. (src, samples, tests). In my opinion, and
> having worked with many builds, there is no reason to have this level of
> complexity or number of makefiles.
>
> John Hawkins
>
>
>
>
>
>              Kenneth Chiu
>              <chiuk@cs.indiana
>              .edu>                                                      To
>                                        Apache AXIS C Developers List
>              11/06/2004 12:09          <ax...@ws.apache.org>
>                                                                         cc
>
>              Please respond to                                     Subject
>               "Apache AXIS C           Re: configure.ac
>              Developers List"
>
>
>
>
>
>
>
>
>
> The usual practice for something like this is that you write
> new macros and put them in a common place, then use some way
> to include them.  (There are a number of ways.)
>
> Do 'info aclocal' and look at the sections on macros.
>
> Normally, you don't ship the configure.ac's anyway, so a
> little bit of complexity during the autoconf process doesn't
> affect the end-user.
>
> Just in case you don't know about already, there is an
> on-line autotools book:
>
>     http://sources.redhat.com/autobook/autobook/autobook_toc.html
>
> On Fri, 11 Jun 2004, John Hawkins wrote:
>
> >
> >
> >
> >
> > OK, that's a start. I understand why we need a make file for each tree
> > (kinda)
> >
> > However, I still need to change 8 configure.ac files everytime I want to
> > port to AIX (or another platform with issues). That's not very portable.
> >
> > Looking at my original listing I see the following configure files
> (minus
> > the ones you've just removed)
> >
> >
> > > ./configure.ac                                - the top level
> > > ./samples/client/configure.ac                       - samples
> > > ./samples/client/testHandler/configure.ac                 - samples
> > > ./samples/server/configure.ac                       - samples
> > > ./src/server/handlers/global/testhandler1/configure.ac    - handler
> > samples or tests?
> > > ./src/server/handlers/transport/testhandler2/configure.ac - handlers
> > samples or tests?
> > > ./src/wcg/configure.ac                              - what is this ?
> > > ./src/xml/txpp/lib/configure.ac                     - what is this?
> > > ./tests/configure.ac                          - tests
> >
> > Few observations -
> > Why do we have lots of different sample files - Surely we just need one
> for
> > the samples tree
> > Samples and/or tests seem be scattered throughout the code base?
> >
> > I also need to understand why we don't have a more simple structure with
> > say a configure file for the following :
> > src
> > tests
> > samples
> >
> > Alternatively we could have one big tree structure with say
> >
> > src
> > src/samples
> > src/tests
> >
> > then I could have one configure.ac file at the top level?
> > If I wanted to build "all" I could or I could pick and choose which I
> > wanted.
> >
> > That would seem more logical to me and far more easy to maintain and port
> ?
> >
> > I appreciate the code has "grown up" but I don't think that I'm way out
> of
> > line here am I?
> >
> > what do people think?
> >
> >
> >
> >
> > John Hawkins
> >
> >
> >
> >
> >
> >              damitha@opensourc
> >              e.lk
> >
> To
> >              11/06/2004 08:54          "Apache AXIS C Developers List"
> >                                        <ax...@ws.apache.org>
> >
> cc
> >              Please respond to
> >               "Apache AXIS C
> Subject
> >              Developers List"          Re: configure.ac
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi John,
> >    Actuall following file are not needed. I removed them
> >    ./samples/server/echoStringHeaderHandler/configure.ac
> >   ./samples/server/interoptests/doclitbase/configure.ac
> >   ./samples/server/interoptests/doclitgroupB/configure.ac
> >
> > 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.
> >
> > damitha
> > >
> > >
> > > Hi Folks,
> > >
> > > Trying to get the latest code building on AIX.
> > >
> > > The compiler I'm using is not understanding the CPPFlags but I know
> what
> > > to
> > > set them to. My question is - if I change configure.ac in the c
> directory
> > > why are there other configure.ac's in other directories (listed below)
> ->
> > >
> > > /home/hawkeye/axis12
> > > # find . -name configure.ac -print
> > > ./configure.ac
> > > ./samples/client/configure.ac
> > > ./samples/client/testHandler/configure.ac
> > > ./samples/server/configure.ac
> > > ./samples/server/echoStringHeaderHandler/configure.ac
> > > ./samples/server/interoptests/doclitbase/configure.ac
> > > ./samples/server/interoptests/doclitgroupB/configure.ac
> > > ./src/server/handlers/global/testhandler1/configure.ac
> > > ./src/server/handlers/transport/testhandler2/configure.ac
> > > ./src/wcg/configure.ac
> > > ./src/xml/txpp/lib/configure.ac
> > > ./tests/configure.ac
> > >
> > > I think what's happening is that when I run build.sh, configure is
> > picking
> > > up the configure.ac files in the different directories. I don't want to
> > > change the configure.ac files for all these directories everytime I
> want
> > > to
> > > build on a new platform so, what can we do? Why do we have all these
> > > configure.ac files ?  Why not just have the one root configure.ac file
> > > that
> > > holds the flags for that platform?
> > >
> > > thanks for any help (Ignorance plays a large part in my questions so
> bare
> > > with me :-)
> > >
> > > John Hawkins
> > >
> > >
> > >
> >
> >
> >
>
>

Re: configure.ac

Posted by da...@opensource.lk.
> Hi John,
>     I thnk you just need 4 configure.ac files
> 1. ./configure.ac                                - the top level
> 2. ./samples/client/configure.ac                       - samples
> 3. ./samples/server/configure.ac                       - samples
> 4. ./tests/configure.ac                          - tests
>
> However, there is no argument that even 4 is too much.
> As an immediate solution what could be done it to include 2, 3 and 4 above
> in 1.
>
> This way it will come down to a single configure.ac.
>
> Thanks,
> Samisa..
>
> --- John Hawkins <HA...@uk.ibm.com> wrote:
>>
>>
>>
>>
>> Hi Kenneth,
>>
>> I appreciate that the end-user has no issues with this -  I'm coming
>> from
>> the viewpoint of having to compile Axis C on X different platforms
>> (where
>> X> 5 let's put it that way). Therefore I don't want to make 8*5 changes
>> (plus any other things I have to do) on every platform . I thought the
>> point of libtools was that they encapsulated platform specific issues
>> into
>> their structure?
>>
>> My points still hold about the fact that we have 8 configure files for a
>> not very big project. When, in my humble opinion, we could either have
>> one
>> (src)or a maximum of three. (src, samples, tests). In my opinion, and
>> having worked with many builds, there is no reason to have this level of
>> complexity or number of makefiles.
>>
>> John Hawkins
>>
>>
>>
>>
>>
>>              Kenneth Chiu
>>              <chiuk@cs.indiana
>>              .edu>
>> To
>>                                        Apache AXIS C Developers List
>>              11/06/2004 12:09          <ax...@ws.apache.org>
>>                                                                         cc
>>
>>              Please respond to
>> Subject
>>               "Apache AXIS C           Re: configure.ac
>>              Developers List"
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> The usual practice for something like this is that you write
>> new macros and put them in a common place, then use some way
>> to include them.  (There are a number of ways.)
>>
>> Do 'info aclocal' and look at the sections on macros.
>>
>> Normally, you don't ship the configure.ac's anyway, so a
>> little bit of complexity during the autoconf process doesn't
>> affect the end-user.
>>
>> Just in case you don't know about already, there is an
>> on-line autotools book:
>>
>>     http://sources.redhat.com/autobook/autobook/autobook_toc.html
>>
>> On Fri, 11 Jun 2004, John Hawkins wrote:
>>
>> >
>> >
>> >
>> >
>> > OK, that's a start. I understand why we need a make file for each tree
>> > (kinda)
>> >
>> > However, I still need to change 8 configure.ac files everytime I want
>> to
>> > port to AIX (or another platform with issues). That's not very
>> portable.
>> >
>> > Looking at my original listing I see the following configure files
>> (minus
>> > the ones you've just removed)
>> >
>> >
>> > > ./configure.ac                                - the top level
>> > > ./samples/client/configure.ac                       - samples
>> > > ./samples/client/testHandler/configure.ac                 - samples
>> > > ./samples/server/configure.ac                       - samples
>> > > ./src/server/handlers/global/testhandler1/configure.ac    - handler
>> > samples or tests?
>> > > ./src/server/handlers/transport/testhandler2/configure.ac - handlers
>> > samples or tests?
>> > > ./src/wcg/configure.ac                              - what is this ?
>> > > ./src/xml/txpp/lib/configure.ac                     - what is this?
>> > > ./tests/configure.ac                          - tests
>> >
>> > Few observations -
>> > Why do we have lots of different sample files - Surely we just need
>> one
>> for
>> > the samples tree
>> > Samples and/or tests seem be scattered throughout the code base?
>> >
>> > I also need to understand why we don't have a more simple structure
>> with
>> > say a configure file for the following :
>> > src
>> > tests
>> > samples
>> >
>> > Alternatively we could have one big tree structure with say
>> >
>> > src
>> > src/samples
>> > src/tests
>> >
>> > then I could have one configure.ac file at the top level?
>> > If I wanted to build "all" I could or I could pick and choose which I
>> > wanted.
>> >
>> > That would seem more logical to me and far more easy to maintain and
>> port
>> ?
>> >
>> > I appreciate the code has "grown up" but I don't think that I'm way
>> out
>> of
>> > line here am I?
>> >
>> > what do people think?
>> >
>> >
>> >
>> >
>> > John Hawkins
>> >
>> >
>> >
>> >
>> >
>> >              damitha@opensourc
>> >              e.lk
>> >
>> To
>> >              11/06/2004 08:54          "Apache AXIS C Developers List"
>> >                                        <ax...@ws.apache.org>
>> >
>> cc
>> >              Please respond to
>> >               "Apache AXIS C
>> Subject
>> >              Developers List"          Re: configure.ac
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > Hi John,
>> >    Actuall following file are not needed. I removed them
>> >    ./samples/server/echoStringHeaderHandler/configure.ac
>> >   ./samples/server/interoptests/doclitbase/configure.ac
>> >   ./samples/server/interoptests/doclitgroupB/configure.ac
>> >
>> > 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.
>> >
>> > damitha
>> > >
>> > >
>> > > Hi Folks,
>> > >
>> > > Trying to get the latest code building on AIX.
>> > >
>> > > The compiler I'm using is not understanding the CPPFlags but I know
>> what
>> > > to
>> > > set them to. My question is - if I change configure.ac in the c
>> directory
>> > > why are there other configure.ac's in other directories (listed
>> below)
>> ->
>> > >
>> > > /home/hawkeye/axis12
>> > > # find . -name configure.ac -print
>> > > ./configure.ac
>> > > ./samples/client/configure.ac
>> > > ./samples/client/testHandler/configure.ac
>> > > ./samples/server/configure.ac
>> > > ./samples/server/echoStringHeaderHandler/configure.ac
>> > > ./samples/server/interoptests/doclitbase/configure.ac
>> > > ./samples/server/interoptests/doclitgroupB/configure.ac
>> > > ./src/server/handlers/global/testhandler1/configure.ac
>> > > ./src/server/handlers/transport/testhandler2/configure.ac
>> > > ./src/wcg/configure.ac
>> > > ./src/xml/txpp/lib/configure.ac
>> > > ./tests/configure.ac
>> > >
>> > > I think what's happening is that when I run build.sh, configure is
>> > picking
>> > > up the configure.ac files in the different directories. I don't want
>> to
>> > > change the configure.ac files for all these directories everytime I
>> want
>> > > to
>> > > build on a new platform so, what can we do? Why do we have all these
>> > > configure.ac files ?  Why not just have the one root configure.ac
>> file
>> > > that
>>
> === message truncated ===
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Friends.  Fun.  Try the all-new Yahoo! Messenger.
> http://messenger.yahoo.com/
>
>


Re: configure.ac

Posted by Aleksander Slominski <as...@cs.indiana.edu>.
+1 and it may be good idea to look on some leading open source projects 
how they approach configuration business.

thanks,

alek

damitha@opensource.lk wrote:

>Hi,
>    Yes we need only one configuration.ac file at root level. I'll do that
>asap. (waiting.....) Actually I did it just now, for release 1.2. Now
>the next requered thing is to have parer selection etc as configure
>parameters.
>
>damitha
>
>  
>
>>Hi John,
>>    I thnk you just need 4 configure.ac files
>>1. ./configure.ac                                - the top level
>>2. ./samples/client/configure.ac                       - samples
>>3. ./samples/server/configure.ac                       - samples
>>4. ./tests/configure.ac                          - tests
>>
>>However, there is no argument that even 4 is too much.
>>As an immediate solution what could be done it to include 2, 3 and 4 above
>>in 1.
>>
>>This way it will come down to a single configure.ac.
>>
>>Thanks,
>>Samisa..
>>
>>--- John Hawkins <HA...@uk.ibm.com> wrote:
>>    
>>
>>>
>>>
>>>Hi Kenneth,
>>>
>>>I appreciate that the end-user has no issues with this -  I'm coming
>>>from
>>>the viewpoint of having to compile Axis C on X different platforms
>>>(where
>>>X> 5 let's put it that way). Therefore I don't want to make 8*5 changes
>>>(plus any other things I have to do) on every platform . I thought the
>>>point of libtools was that they encapsulated platform specific issues
>>>into
>>>their structure?
>>>
>>>My points still hold about the fact that we have 8 configure files for a
>>>not very big project. When, in my humble opinion, we could either have
>>>one
>>>(src)or a maximum of three. (src, samples, tests). In my opinion, and
>>>having worked with many builds, there is no reason to have this level of
>>>complexity or number of makefiles.
>>>
>>>John Hawkins
>>>
>>>
>>>
>>>
>>>
>>>             Kenneth Chiu
>>>             <chiuk@cs.indiana
>>>             .edu>
>>>To
>>>                                       Apache AXIS C Developers List
>>>             11/06/2004 12:09          <ax...@ws.apache.org>
>>>                                                                        cc
>>>
>>>             Please respond to
>>>Subject
>>>              "Apache AXIS C           Re: configure.ac
>>>             Developers List"
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>The usual practice for something like this is that you write
>>>new macros and put them in a common place, then use some way
>>>to include them.  (There are a number of ways.)
>>>
>>>Do 'info aclocal' and look at the sections on macros.
>>>
>>>Normally, you don't ship the configure.ac's anyway, so a
>>>little bit of complexity during the autoconf process doesn't
>>>affect the end-user.
>>>
>>>Just in case you don't know about already, there is an
>>>on-line autotools book:
>>>
>>>    http://sources.redhat.com/autobook/autobook/autobook_toc.html
>>>
>>>On Fri, 11 Jun 2004, John Hawkins wrote:
>>>
>>>      
>>>
>>>>
>>>>
>>>>OK, that's a start. I understand why we need a make file for each tree
>>>>(kinda)
>>>>
>>>>However, I still need to change 8 configure.ac files everytime I want
>>>>        
>>>>
>>>to
>>>      
>>>
>>>>port to AIX (or another platform with issues). That's not very
>>>>        
>>>>
>>>portable.
>>>      
>>>
>>>>Looking at my original listing I see the following configure files
>>>>        
>>>>
>>>(minus
>>>      
>>>
>>>>the ones you've just removed)
>>>>
>>>>
>>>>        
>>>>
>>>>>./configure.ac                                - the top level
>>>>>./samples/client/configure.ac                       - samples
>>>>>./samples/client/testHandler/configure.ac                 - samples
>>>>>./samples/server/configure.ac                       - samples
>>>>>./src/server/handlers/global/testhandler1/configure.ac    - handler
>>>>>          
>>>>>
>>>>samples or tests?
>>>>        
>>>>
>>>>>./src/server/handlers/transport/testhandler2/configure.ac - handlers
>>>>>          
>>>>>
>>>>samples or tests?
>>>>        
>>>>
>>>>>./src/wcg/configure.ac                              - what is this ?
>>>>>./src/xml/txpp/lib/configure.ac                     - what is this?
>>>>>./tests/configure.ac                          - tests
>>>>>          
>>>>>
>>>>Few observations -
>>>>Why do we have lots of different sample files - Surely we just need
>>>>        
>>>>
>>>one
>>>for
>>>      
>>>
>>>>the samples tree
>>>>Samples and/or tests seem be scattered throughout the code base?
>>>>
>>>>I also need to understand why we don't have a more simple structure
>>>>        
>>>>
>>>with
>>>      
>>>
>>>>say a configure file for the following :
>>>>src
>>>>tests
>>>>samples
>>>>
>>>>Alternatively we could have one big tree structure with say
>>>>
>>>>src
>>>>src/samples
>>>>src/tests
>>>>
>>>>then I could have one configure.ac file at the top level?
>>>>If I wanted to build "all" I could or I could pick and choose which I
>>>>wanted.
>>>>
>>>>That would seem more logical to me and far more easy to maintain and
>>>>        
>>>>
>>>port
>>>?
>>>      
>>>
>>>>I appreciate the code has "grown up" but I don't think that I'm way
>>>>        
>>>>
>>>out
>>>of
>>>      
>>>
>>>>line here am I?
>>>>
>>>>what do people think?
>>>>
>>>>
>>>>
>>>>
>>>>John Hawkins
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>             damitha@opensourc
>>>>             e.lk
>>>>
>>>>        
>>>>
>>>To
>>>      
>>>
>>>>             11/06/2004 08:54          "Apache AXIS C Developers List"
>>>>                                       <ax...@ws.apache.org>
>>>>
>>>>        
>>>>
>>>cc
>>>      
>>>
>>>>             Please respond to
>>>>              "Apache AXIS C
>>>>        
>>>>
>>>Subject
>>>      
>>>
>>>>             Developers List"          Re: configure.ac
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>Hi John,
>>>>   Actuall following file are not needed. I removed them
>>>>   ./samples/server/echoStringHeaderHandler/configure.ac
>>>>  ./samples/server/interoptests/doclitbase/configure.ac
>>>>  ./samples/server/interoptests/doclitgroupB/configure.ac
>>>>
>>>>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.
>>>>
>>>>damitha
>>>>        
>>>>
>>>>>Hi Folks,
>>>>>
>>>>>Trying to get the latest code building on AIX.
>>>>>
>>>>>The compiler I'm using is not understanding the CPPFlags but I know
>>>>>          
>>>>>
>>>what
>>>      
>>>
>>>>>to
>>>>>set them to. My question is - if I change configure.ac in the c
>>>>>          
>>>>>
>>>directory
>>>      
>>>
>>>>>why are there other configure.ac's in other directories (listed
>>>>>          
>>>>>
>>>below)
>>>->
>>>      
>>>
>>>>>/home/hawkeye/axis12
>>>>># find . -name configure.ac -print
>>>>>./configure.ac
>>>>>./samples/client/configure.ac
>>>>>./samples/client/testHandler/configure.ac
>>>>>./samples/server/configure.ac
>>>>>./samples/server/echoStringHeaderHandler/configure.ac
>>>>>./samples/server/interoptests/doclitbase/configure.ac
>>>>>./samples/server/interoptests/doclitgroupB/configure.ac
>>>>>./src/server/handlers/global/testhandler1/configure.ac
>>>>>./src/server/handlers/transport/testhandler2/configure.ac
>>>>>./src/wcg/configure.ac
>>>>>./src/xml/txpp/lib/configure.ac
>>>>>./tests/configure.ac
>>>>>
>>>>>I think what's happening is that when I run build.sh, configure is
>>>>>          
>>>>>
>>>>picking
>>>>        
>>>>
>>>>>up the configure.ac files in the different directories. I don't want
>>>>>          
>>>>>
>>>to
>>>      
>>>
>>>>>change the configure.ac files for all these directories everytime I
>>>>>          
>>>>>
>>>want
>>>      
>>>
>>>>>to
>>>>>build on a new platform so, what can we do? Why do we have all these
>>>>>configure.ac files ?  Why not just have the one root configure.ac
>>>>>          
>>>>>
>>>file
>>>      
>>>
>>>>>that
>>>>>          
>>>>>
>>=== message truncated ===
>>
>>
>>
>>
>>
>>__________________________________
>>Do you Yahoo!?
>>Friends.  Fun.  Try the all-new Yahoo! Messenger.
>>http://messenger.yahoo.com/
>>
>>
>>    
>>
>
>  
>


-- 
The best way to predict the future is to invent it - Alan Kay


RE: suporting contributions (or not ...)

Posted by Susantha Kumara <su...@opensource.lk>.
> -----Original Message-----
> From: Aleksander Slominski [mailto:aslom@cs.indiana.edu]
> Sent: Tuesday, June 15, 2004 9:38 AM
> To: Apache AXIS C Developers List
> Subject: suporting contributions (or not ...)
> 
> Samisa Abeysinghe wrote:
> 
> >    I am kind of frustrated on the amount of rework/rechecks that I
have
> to do. Please fix the
> >Stub/parser abstraction and trasport abstraction documentation, so
that
> users could program using
> >those.
> >
> >
> 
> Samisa,
> 
> i can only second this. to this day i still do not know why WSDL2WS
has so
> much code copied from (some version of) AXIS-Java that so easily gets
out
> of sync and there is no unit tests to verify what modifications were
added

Yes I too asked the original developer Srinath who wrote the code to
extract the WSDL information from the SymbolTable class about this.

Srinath: could you please help us to understand why this. I mean
overriding ElementDecl class etc


> ...
> 
> thanks,
> 
> alek
> 
> --
> The best way to predict the future is to invent it - Alan Kay



suporting contributions (or not ...)

Posted by Aleksander Slominski <as...@cs.indiana.edu>.
Samisa Abeysinghe wrote:

>    I am kind of frustrated on the amount of rework/rechecks that I have to do. Please fix the
>Stub/parser abstraction and trasport abstraction documentation, so that users could program using
>those.
>  
>

Samisa,

i can only second this. to this day i still do not know why WSDL2WS has so much code copied from (some version of) AXIS-Java that so easily gets out of sync and there is no unit tests to verify what modifications were added ...

thanks,

alek

-- 
The best way to predict the future is to invent it - Alan Kay


RE: API doc generation with Doxygen

Posted by Samisa Abeysinghe <sa...@yahoo.com>.
> attractive. Does somebody know how to make the index page more informative
> and have some introduction like thing.

http://www.stack.nl/~dimitri/doxygen/faq.html

How to get information on the index page in HTML?

You should use the \mainpage command inside a comment block like this:

/*! \mainpage My Personal Index Page 
* * \section intro_sec Introduction 
* * This is the introduction. 
* * \section install_sec Installation 
* * \subsection step1 Step 1: Opening the box 
* * etc... */ 

Samisa...


	
		
__________________________________
Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/ 

RE: API doc generation with Doxygen

Posted by da...@opensource.lk.
+1 for that suggestion,
because generating the api from doxygenconf is very simple process.
I think that the generated doxygen api's pages index file is not very
attractive. Does somebody know how to make the index page more informative
and have some introduction like thing.

damitha
> Hi Samisa,
>
> I think this has happened with my commit with documentation of Parser
> and Transport related header files. Actually I did not try to generate
> the API documentation with doxygen before commiting. I only compiled and
> ran Axis to verify that it works and commited. I apologize for any
> inconvenience caused.
>
> Shall we make the tradition from now on that any developer should also
> run doxygen any verify correct API doc generation before commiting.
>
>
>> -----Original Message-----
>> From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
>> Sent: Tuesday, June 15, 2004 8:46 AM
>> To: Apache AXIS C Developers List
>> Subject: API doc generation with Doxygen
>>
>> Hi,
>>     I updated the Stub.h and made sure the API doc comments work with
>> doxygen.
>>
>>     However the latest changes done on the file by someone else has
> made
>> the doxygen tool not to
>> pick the comments and does not generate properly.
>
> That was my mistake. I am sorry for that.
>
>>     This is the second time around that the work done by me was made
> non
>> functional. (the earlier
>> situation was in case of the WSDL2WS tool)
>>     I think we better have some diciplined testing before commits are
>> made.
>
> Yes this is not the first time that this has happened. I today found
> that WSDL2Ws tool does not generate the default constructor of client
> side stub with the endpoint taken from the WSDL. Some one has removed
> that part of code in WSDL2Ws tool.
>
> We have to avoid happening these in the future.
>
>>
>>     In case of doxygen please make sure to verify that documents are
>> generated properly.
>>
>>     Additionally, I cannot locate docs related to Transport
> abstraction
>> and parser abstraction
>> within the API docs generated.
>>
>>     I am kind of frustrated on the amount of rework/rechecks that I
> have
>> to do. Please fix the
>> Stub/parser abstraction and trasport abstraction documentation, so
> that
>> users could program using
>> those.
>>
>> Thanks,
>> Samisa...
>>
>
> Thanks,
> --
> Susantha Kumara
> Lanka Software Foundation
> Office : +94112591785
> Mobile : +94777420453
>
>
>


pre-commit checks [Re: API doc generation with Doxygen

Posted by Aleksander Slominski <as...@cs.indiana.edu>.
hi,

instead of relying on tradition i would suggest to add pre-commit target 
(to makefile or build.xml <-- java is required anyway to compile 
wsdl2ws) and have it recompile all code, run unit tests and call doxygen.

only if all of above succeeds one should do check in.

what happened to nightly builds? they could do the same pre-commit 
checks on nightly basis.

thanks,

alek

Samisa Abeysinghe wrote:

>Hi Susantha,
>    Is it possible for you to fix the problems.
>    I cannot still generate the docs.
>Thanks,
>Samisa
>
>
>--- Susantha Kumara <su...@opensource.lk> wrote:
>  
>
>>Hi Samisa,
>>
>>I think this has happened with my commit with documentation of Parser
>>and Transport related header files. Actually I did not try to generate
>>the API documentation with doxygen before commiting. I only compiled and
>>ran Axis to verify that it works and commited. I apologize for any
>>inconvenience caused.
>>
>>Shall we make the tradition from now on that any developer should also
>>run doxygen any verify correct API doc generation before commiting. 
>>
>>
>>    
>>
>>>-----Original Message-----
>>>From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
>>>Sent: Tuesday, June 15, 2004 8:46 AM
>>>To: Apache AXIS C Developers List
>>>Subject: API doc generation with Doxygen
>>>
>>>Hi,
>>>    I updated the Stub.h and made sure the API doc comments work with
>>>doxygen.
>>>
>>>    However the latest changes done on the file by someone else has
>>>      
>>>
>>made
>>    
>>
>>>the doxygen tool not to
>>>pick the comments and does not generate properly.
>>>      
>>>
>>That was my mistake. I am sorry for that.
>> 
>>    
>>
>>>    This is the second time around that the work done by me was made
>>>      
>>>
>>non
>>    
>>
>>>functional. (the earlier
>>>situation was in case of the WSDL2WS tool)
>>>    I think we better have some diciplined testing before commits are
>>>made.
>>>      
>>>
>>Yes this is not the first time that this has happened. I today found
>>that WSDL2Ws tool does not generate the default constructor of client
>>side stub with the endpoint taken from the WSDL. Some one has removed
>>that part of code in WSDL2Ws tool.
>> 
>>We have to avoid happening these in the future.
>>
>>    
>>
>>>    In case of doxygen please make sure to verify that documents are
>>>generated properly.
>>>
>>>    Additionally, I cannot locate docs related to Transport
>>>      
>>>
>>abstraction
>>    
>>
>>>and parser abstraction
>>>within the API docs generated.
>>>
>>>    I am kind of frustrated on the amount of rework/rechecks that I
>>>      
>>>
>>have
>>    
>>
>>>to do. Please fix the
>>>Stub/parser abstraction and trasport abstraction documentation, so
>>>      
>>>
>>that
>>    
>>
>>>users could program using
>>>those.
>>>
>>>Thanks,
>>>Samisa...
>>>
>>>      
>>>
>>Thanks,
>>--
>>Susantha Kumara
>>Lanka Software Foundation
>>Office : +94112591785
>>Mobile : +94777420453
>>
>>
>>    
>>
>
>
>
>	
>		
>__________________________________
>Do you Yahoo!?
>Friends.  Fun.  Try the all-new Yahoo! Messenger.
>http://messenger.yahoo.com/ 
>  
>


-- 
The best way to predict the future is to invent it - Alan Kay


RE: API doc generation with Doxygen

Posted by Susantha Kumara <su...@opensource.lk>.
Hi Samisa,

I read some doxygen docs at,

file:/usr/share/doc/doxygen-doc/html/index.html

and found the problem.

The problem was we had following line in doxygenconf 

ENABLE_PREPROCESSING   = YES

This line says doxygen to consider the C preprocessor directives and as
we have not defined __cplusplus in doxygenconf any code wrapped with
#ifdef __cplusplus ... #endif are ignored.

Its usefull that we turn off preprocessing because we need documentation
to be generated for everything (irrespective of compiler directives).

so I made 

ENABLE_PREPROCESSING   = NO

Thanks,

Susantha
---

On Wed, 2004-06-16 at 09:54, Samisa Abeysinghe wrote:
> May be the problem is that there are 2 classes/structs in the header file.
> I think doxygen is capable of hadling this situation.
> If not we can move the classes to seperate headers.
> 
> Thanks,
> Samisa...
> 
> --- Susantha Kumara <su...@opensource.lk> wrote:
> > Hi Samisa,
> > 
> > I checked the doxygen comments. But I could not yet locate the problem.
> > I will try to locate the problem ASAP.
> > 
> > ---
> > Susantha
> > 
> > > -----Original Message-----
> > > From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
> > > Sent: Tuesday, June 15, 2004 1:00 PM
> > > To: Apache AXIS C Developers List
> > > Subject: RE: API doc generation with Doxygen
> > > 
> > > Hi Susantha,
> > >     Is it possible for you to fix the problems.
> > >     I cannot still generate the docs.
> > > Thanks,
> > > Samisa
> > > 
> > > 
> > > --- Susantha Kumara <su...@opensource.lk> wrote:
> > > > Hi Samisa,
> > > >
> > > > I think this has happened with my commit with documentation of
> > Parser
> > > > and Transport related header files. Actually I did not try to
> > generate
> > > > the API documentation with doxygen before commiting. I only compiled
> > and
> > > > ran Axis to verify that it works and commited. I apologize for any
> > > > inconvenience caused.
> > > >
> > > > Shall we make the tradition from now on that any developer should
> > also
> > > > run doxygen any verify correct API doc generation before commiting.
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
> > > > > Sent: Tuesday, June 15, 2004 8:46 AM
> > > > > To: Apache AXIS C Developers List
> > > > > Subject: API doc generation with Doxygen
> > > > >
> > > > > Hi,
> > > > >     I updated the Stub.h and made sure the API doc comments work
> > with
> > > > > doxygen.
> > > > >
> > > > >     However the latest changes done on the file by someone else
> > has
> > > > made
> > > > > the doxygen tool not to
> > > > > pick the comments and does not generate properly.
> > > >
> > > > That was my mistake. I am sorry for that.
> > > >
> > > > >     This is the second time around that the work done by me was
> > made
> > > > non
> > > > > functional. (the earlier
> > > > > situation was in case of the WSDL2WS tool)
> > > > >     I think we better have some diciplined testing before commits
> > are
> > > > > made.
> > > >
> > > > Yes this is not the first time that this has happened. I today found
> > > > that WSDL2Ws tool does not generate the default constructor of
> > client
> > > > side stub with the endpoint taken from the WSDL. Some one has
> > removed
> > > > that part of code in WSDL2Ws tool.
> > > >
> > > > We have to avoid happening these in the future.
> > > >
> > > > >
> > > > >     In case of doxygen please make sure to verify that documents
> > are
> > > > > generated properly.
> > > > >
> > > > >     Additionally, I cannot locate docs related to Transport
> > > > abstraction
> > > > > and parser abstraction
> > > > > within the API docs generated.
> > > > >
> > > > >     I am kind of frustrated on the amount of rework/rechecks that
> > I
> > > > have
> > > > > to do. Please fix the
> > > > > Stub/parser abstraction and trasport abstraction documentation, so
> > > > that
> > > > > users could program using
> > > > > those.
> > > > >
> > > > > Thanks,
> > > > > Samisa...
> > > > >
> > > >
> > > > Thanks,
> > > > --
> > > > Susantha Kumara
> > > > Lanka Software Foundation
> > > > Office : +94112591785
> > > > Mobile : +94777420453
> > > >
> > > >
> > > 
> > > 
> > > 
> > > 
> > > 
> > > __________________________________
> > > Do you Yahoo!?
> > > Friends.  Fun.  Try the all-new Yahoo! Messenger.
> > > http://messenger.yahoo.com/
> > 
> > 
> 
> 
> 
> 		
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail Address AutoComplete - You start. We finish.
> http://promotions.yahoo.com/new_mail
> 


API docs

Posted by Samisa Abeysinghe <sa...@yahoo.com>.
Hi all,
    I generated the API docs with cvs using doxygen and it works!!

    Now I have few throughts
1. There are some classes that are not documented in the generated API doc. Are they not required
by the user?

2. As I know, there is an option in doxygen to group classes into groups.
We have the following sections in Axis C++. Can we group the classes in API docs generated?
Trasport abstraction
Parser abstraction
Stub
Exceptions
Handlers

3. We could add comments to appear in the index page of the generated  API. I think it would be
nice to have some index page.

Thanks,
Samisa...



	
		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail 

RE: API doc generation with Doxygen

Posted by Samisa Abeysinghe <sa...@yahoo.com>.
May be the problem is that there are 2 classes/structs in the header file.
I think doxygen is capable of hadling this situation.
If not we can move the classes to seperate headers.

Thanks,
Samisa...

--- Susantha Kumara <su...@opensource.lk> wrote:
> Hi Samisa,
> 
> I checked the doxygen comments. But I could not yet locate the problem.
> I will try to locate the problem ASAP.
> 
> ---
> Susantha
> 
> > -----Original Message-----
> > From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
> > Sent: Tuesday, June 15, 2004 1:00 PM
> > To: Apache AXIS C Developers List
> > Subject: RE: API doc generation with Doxygen
> > 
> > Hi Susantha,
> >     Is it possible for you to fix the problems.
> >     I cannot still generate the docs.
> > Thanks,
> > Samisa
> > 
> > 
> > --- Susantha Kumara <su...@opensource.lk> wrote:
> > > Hi Samisa,
> > >
> > > I think this has happened with my commit with documentation of
> Parser
> > > and Transport related header files. Actually I did not try to
> generate
> > > the API documentation with doxygen before commiting. I only compiled
> and
> > > ran Axis to verify that it works and commited. I apologize for any
> > > inconvenience caused.
> > >
> > > Shall we make the tradition from now on that any developer should
> also
> > > run doxygen any verify correct API doc generation before commiting.
> > >
> > >
> > > > -----Original Message-----
> > > > From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
> > > > Sent: Tuesday, June 15, 2004 8:46 AM
> > > > To: Apache AXIS C Developers List
> > > > Subject: API doc generation with Doxygen
> > > >
> > > > Hi,
> > > >     I updated the Stub.h and made sure the API doc comments work
> with
> > > > doxygen.
> > > >
> > > >     However the latest changes done on the file by someone else
> has
> > > made
> > > > the doxygen tool not to
> > > > pick the comments and does not generate properly.
> > >
> > > That was my mistake. I am sorry for that.
> > >
> > > >     This is the second time around that the work done by me was
> made
> > > non
> > > > functional. (the earlier
> > > > situation was in case of the WSDL2WS tool)
> > > >     I think we better have some diciplined testing before commits
> are
> > > > made.
> > >
> > > Yes this is not the first time that this has happened. I today found
> > > that WSDL2Ws tool does not generate the default constructor of
> client
> > > side stub with the endpoint taken from the WSDL. Some one has
> removed
> > > that part of code in WSDL2Ws tool.
> > >
> > > We have to avoid happening these in the future.
> > >
> > > >
> > > >     In case of doxygen please make sure to verify that documents
> are
> > > > generated properly.
> > > >
> > > >     Additionally, I cannot locate docs related to Transport
> > > abstraction
> > > > and parser abstraction
> > > > within the API docs generated.
> > > >
> > > >     I am kind of frustrated on the amount of rework/rechecks that
> I
> > > have
> > > > to do. Please fix the
> > > > Stub/parser abstraction and trasport abstraction documentation, so
> > > that
> > > > users could program using
> > > > those.
> > > >
> > > > Thanks,
> > > > Samisa...
> > > >
> > >
> > > Thanks,
> > > --
> > > Susantha Kumara
> > > Lanka Software Foundation
> > > Office : +94112591785
> > > Mobile : +94777420453
> > >
> > >
> > 
> > 
> > 
> > 
> > 
> > __________________________________
> > Do you Yahoo!?
> > Friends.  Fun.  Try the all-new Yahoo! Messenger.
> > http://messenger.yahoo.com/
> 
> 



		
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail 

RE: API doc generation with Doxygen

Posted by Susantha Kumara <su...@opensource.lk>.
Hi Samisa,

I checked the doxygen comments. But I could not yet locate the problem.
I will try to locate the problem ASAP.

---
Susantha

> -----Original Message-----
> From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
> Sent: Tuesday, June 15, 2004 1:00 PM
> To: Apache AXIS C Developers List
> Subject: RE: API doc generation with Doxygen
> 
> Hi Susantha,
>     Is it possible for you to fix the problems.
>     I cannot still generate the docs.
> Thanks,
> Samisa
> 
> 
> --- Susantha Kumara <su...@opensource.lk> wrote:
> > Hi Samisa,
> >
> > I think this has happened with my commit with documentation of
Parser
> > and Transport related header files. Actually I did not try to
generate
> > the API documentation with doxygen before commiting. I only compiled
and
> > ran Axis to verify that it works and commited. I apologize for any
> > inconvenience caused.
> >
> > Shall we make the tradition from now on that any developer should
also
> > run doxygen any verify correct API doc generation before commiting.
> >
> >
> > > -----Original Message-----
> > > From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
> > > Sent: Tuesday, June 15, 2004 8:46 AM
> > > To: Apache AXIS C Developers List
> > > Subject: API doc generation with Doxygen
> > >
> > > Hi,
> > >     I updated the Stub.h and made sure the API doc comments work
with
> > > doxygen.
> > >
> > >     However the latest changes done on the file by someone else
has
> > made
> > > the doxygen tool not to
> > > pick the comments and does not generate properly.
> >
> > That was my mistake. I am sorry for that.
> >
> > >     This is the second time around that the work done by me was
made
> > non
> > > functional. (the earlier
> > > situation was in case of the WSDL2WS tool)
> > >     I think we better have some diciplined testing before commits
are
> > > made.
> >
> > Yes this is not the first time that this has happened. I today found
> > that WSDL2Ws tool does not generate the default constructor of
client
> > side stub with the endpoint taken from the WSDL. Some one has
removed
> > that part of code in WSDL2Ws tool.
> >
> > We have to avoid happening these in the future.
> >
> > >
> > >     In case of doxygen please make sure to verify that documents
are
> > > generated properly.
> > >
> > >     Additionally, I cannot locate docs related to Transport
> > abstraction
> > > and parser abstraction
> > > within the API docs generated.
> > >
> > >     I am kind of frustrated on the amount of rework/rechecks that
I
> > have
> > > to do. Please fix the
> > > Stub/parser abstraction and trasport abstraction documentation, so
> > that
> > > users could program using
> > > those.
> > >
> > > Thanks,
> > > Samisa...
> > >
> >
> > Thanks,
> > --
> > Susantha Kumara
> > Lanka Software Foundation
> > Office : +94112591785
> > Mobile : +94777420453
> >
> >
> 
> 
> 
> 
> 
> __________________________________
> Do you Yahoo!?
> Friends.  Fun.  Try the all-new Yahoo! Messenger.
> http://messenger.yahoo.com/


RE: API doc generation with Doxygen

Posted by Samisa Abeysinghe <sa...@yahoo.com>.
Hi Susantha,
    Is it possible for you to fix the problems.
    I cannot still generate the docs.
Thanks,
Samisa


--- Susantha Kumara <su...@opensource.lk> wrote:
> Hi Samisa,
> 
> I think this has happened with my commit with documentation of Parser
> and Transport related header files. Actually I did not try to generate
> the API documentation with doxygen before commiting. I only compiled and
> ran Axis to verify that it works and commited. I apologize for any
> inconvenience caused.
> 
> Shall we make the tradition from now on that any developer should also
> run doxygen any verify correct API doc generation before commiting. 
> 
> 
> > -----Original Message-----
> > From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
> > Sent: Tuesday, June 15, 2004 8:46 AM
> > To: Apache AXIS C Developers List
> > Subject: API doc generation with Doxygen
> > 
> > Hi,
> >     I updated the Stub.h and made sure the API doc comments work with
> > doxygen.
> > 
> >     However the latest changes done on the file by someone else has
> made
> > the doxygen tool not to
> > pick the comments and does not generate properly.
> 
> That was my mistake. I am sorry for that.
>  
> >     This is the second time around that the work done by me was made
> non
> > functional. (the earlier
> > situation was in case of the WSDL2WS tool)
> >     I think we better have some diciplined testing before commits are
> > made.
> 
> Yes this is not the first time that this has happened. I today found
> that WSDL2Ws tool does not generate the default constructor of client
> side stub with the endpoint taken from the WSDL. Some one has removed
> that part of code in WSDL2Ws tool.
>  
> We have to avoid happening these in the future.
> 
> > 
> >     In case of doxygen please make sure to verify that documents are
> > generated properly.
> > 
> >     Additionally, I cannot locate docs related to Transport
> abstraction
> > and parser abstraction
> > within the API docs generated.
> > 
> >     I am kind of frustrated on the amount of rework/rechecks that I
> have
> > to do. Please fix the
> > Stub/parser abstraction and trasport abstraction documentation, so
> that
> > users could program using
> > those.
> > 
> > Thanks,
> > Samisa...
> > 
> 
> Thanks,
> --
> Susantha Kumara
> Lanka Software Foundation
> Office : +94112591785
> Mobile : +94777420453
> 
> 



	
		
__________________________________
Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/ 

RE: API doc generation with Doxygen

Posted by Susantha Kumara <su...@opensource.lk>.
Hi Samisa,

I think this has happened with my commit with documentation of Parser
and Transport related header files. Actually I did not try to generate
the API documentation with doxygen before commiting. I only compiled and
ran Axis to verify that it works and commited. I apologize for any
inconvenience caused.

Shall we make the tradition from now on that any developer should also
run doxygen any verify correct API doc generation before commiting. 


> -----Original Message-----
> From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
> Sent: Tuesday, June 15, 2004 8:46 AM
> To: Apache AXIS C Developers List
> Subject: API doc generation with Doxygen
> 
> Hi,
>     I updated the Stub.h and made sure the API doc comments work with
> doxygen.
> 
>     However the latest changes done on the file by someone else has
made
> the doxygen tool not to
> pick the comments and does not generate properly.

That was my mistake. I am sorry for that.
 
>     This is the second time around that the work done by me was made
non
> functional. (the earlier
> situation was in case of the WSDL2WS tool)
>     I think we better have some diciplined testing before commits are
> made.

Yes this is not the first time that this has happened. I today found
that WSDL2Ws tool does not generate the default constructor of client
side stub with the endpoint taken from the WSDL. Some one has removed
that part of code in WSDL2Ws tool.
 
We have to avoid happening these in the future.

> 
>     In case of doxygen please make sure to verify that documents are
> generated properly.
> 
>     Additionally, I cannot locate docs related to Transport
abstraction
> and parser abstraction
> within the API docs generated.
> 
>     I am kind of frustrated on the amount of rework/rechecks that I
have
> to do. Please fix the
> Stub/parser abstraction and trasport abstraction documentation, so
that
> users could program using
> those.
> 
> Thanks,
> Samisa...
> 

Thanks,
--
Susantha Kumara
Lanka Software Foundation
Office : +94112591785
Mobile : +94777420453


API doc generation with Doxygen

Posted by Samisa Abeysinghe <sa...@yahoo.com>.
Hi,
    I updated the Stub.h and made sure the API doc comments work with doxygen.

    However the latest changes done on the file by someone else has made the doxygen tool not to
pick the comments and does not generate properly. 
    This is the second time around that the work done by me was made non functional. (the earlier
situation was in case of the WSDL2WS tool) 
    I think we better have some diciplined testing before commits are made. 
  
    In case of doxygen please make sure to verify that documents are generated properly. 

    Additionally, I cannot locate docs related to Transport abstraction and parser abstraction
within the API docs generated. 

    I am kind of frustrated on the amount of rework/rechecks that I have to do. Please fix the
Stub/parser abstraction and trasport abstraction documentation, so that users could program using
those.

Thanks,
Samisa...


	
		
__________________________________
Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/ 

Re: configure.ac

Posted by da...@opensource.lk.
Hi,
    Yes we need only one configuration.ac file at root level. I'll do that
asap. (waiting.....) Actually I did it just now, for release 1.2. Now
the next requered thing is to have parer selection etc as configure
parameters.

damitha

> Hi John,
>     I thnk you just need 4 configure.ac files
> 1. ./configure.ac                                - the top level
> 2. ./samples/client/configure.ac                       - samples
> 3. ./samples/server/configure.ac                       - samples
> 4. ./tests/configure.ac                          - tests
>
> However, there is no argument that even 4 is too much.
> As an immediate solution what could be done it to include 2, 3 and 4 above
> in 1.
>
> This way it will come down to a single configure.ac.
>
> Thanks,
> Samisa..
>
> --- John Hawkins <HA...@uk.ibm.com> wrote:
>>
>>
>>
>>
>> Hi Kenneth,
>>
>> I appreciate that the end-user has no issues with this -  I'm coming
>> from
>> the viewpoint of having to compile Axis C on X different platforms
>> (where
>> X> 5 let's put it that way). Therefore I don't want to make 8*5 changes
>> (plus any other things I have to do) on every platform . I thought the
>> point of libtools was that they encapsulated platform specific issues
>> into
>> their structure?
>>
>> My points still hold about the fact that we have 8 configure files for a
>> not very big project. When, in my humble opinion, we could either have
>> one
>> (src)or a maximum of three. (src, samples, tests). In my opinion, and
>> having worked with many builds, there is no reason to have this level of
>> complexity or number of makefiles.
>>
>> John Hawkins
>>
>>
>>
>>
>>
>>              Kenneth Chiu
>>              <chiuk@cs.indiana
>>              .edu>
>> To
>>                                        Apache AXIS C Developers List
>>              11/06/2004 12:09          <ax...@ws.apache.org>
>>                                                                         cc
>>
>>              Please respond to
>> Subject
>>               "Apache AXIS C           Re: configure.ac
>>              Developers List"
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> The usual practice for something like this is that you write
>> new macros and put them in a common place, then use some way
>> to include them.  (There are a number of ways.)
>>
>> Do 'info aclocal' and look at the sections on macros.
>>
>> Normally, you don't ship the configure.ac's anyway, so a
>> little bit of complexity during the autoconf process doesn't
>> affect the end-user.
>>
>> Just in case you don't know about already, there is an
>> on-line autotools book:
>>
>>     http://sources.redhat.com/autobook/autobook/autobook_toc.html
>>
>> On Fri, 11 Jun 2004, John Hawkins wrote:
>>
>> >
>> >
>> >
>> >
>> > OK, that's a start. I understand why we need a make file for each tree
>> > (kinda)
>> >
>> > However, I still need to change 8 configure.ac files everytime I want
>> to
>> > port to AIX (or another platform with issues). That's not very
>> portable.
>> >
>> > Looking at my original listing I see the following configure files
>> (minus
>> > the ones you've just removed)
>> >
>> >
>> > > ./configure.ac                                - the top level
>> > > ./samples/client/configure.ac                       - samples
>> > > ./samples/client/testHandler/configure.ac                 - samples
>> > > ./samples/server/configure.ac                       - samples
>> > > ./src/server/handlers/global/testhandler1/configure.ac    - handler
>> > samples or tests?
>> > > ./src/server/handlers/transport/testhandler2/configure.ac - handlers
>> > samples or tests?
>> > > ./src/wcg/configure.ac                              - what is this ?
>> > > ./src/xml/txpp/lib/configure.ac                     - what is this?
>> > > ./tests/configure.ac                          - tests
>> >
>> > Few observations -
>> > Why do we have lots of different sample files - Surely we just need
>> one
>> for
>> > the samples tree
>> > Samples and/or tests seem be scattered throughout the code base?
>> >
>> > I also need to understand why we don't have a more simple structure
>> with
>> > say a configure file for the following :
>> > src
>> > tests
>> > samples
>> >
>> > Alternatively we could have one big tree structure with say
>> >
>> > src
>> > src/samples
>> > src/tests
>> >
>> > then I could have one configure.ac file at the top level?
>> > If I wanted to build "all" I could or I could pick and choose which I
>> > wanted.
>> >
>> > That would seem more logical to me and far more easy to maintain and
>> port
>> ?
>> >
>> > I appreciate the code has "grown up" but I don't think that I'm way
>> out
>> of
>> > line here am I?
>> >
>> > what do people think?
>> >
>> >
>> >
>> >
>> > John Hawkins
>> >
>> >
>> >
>> >
>> >
>> >              damitha@opensourc
>> >              e.lk
>> >
>> To
>> >              11/06/2004 08:54          "Apache AXIS C Developers List"
>> >                                        <ax...@ws.apache.org>
>> >
>> cc
>> >              Please respond to
>> >               "Apache AXIS C
>> Subject
>> >              Developers List"          Re: configure.ac
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > Hi John,
>> >    Actuall following file are not needed. I removed them
>> >    ./samples/server/echoStringHeaderHandler/configure.ac
>> >   ./samples/server/interoptests/doclitbase/configure.ac
>> >   ./samples/server/interoptests/doclitgroupB/configure.ac
>> >
>> > 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.
>> >
>> > damitha
>> > >
>> > >
>> > > Hi Folks,
>> > >
>> > > Trying to get the latest code building on AIX.
>> > >
>> > > The compiler I'm using is not understanding the CPPFlags but I know
>> what
>> > > to
>> > > set them to. My question is - if I change configure.ac in the c
>> directory
>> > > why are there other configure.ac's in other directories (listed
>> below)
>> ->
>> > >
>> > > /home/hawkeye/axis12
>> > > # find . -name configure.ac -print
>> > > ./configure.ac
>> > > ./samples/client/configure.ac
>> > > ./samples/client/testHandler/configure.ac
>> > > ./samples/server/configure.ac
>> > > ./samples/server/echoStringHeaderHandler/configure.ac
>> > > ./samples/server/interoptests/doclitbase/configure.ac
>> > > ./samples/server/interoptests/doclitgroupB/configure.ac
>> > > ./src/server/handlers/global/testhandler1/configure.ac
>> > > ./src/server/handlers/transport/testhandler2/configure.ac
>> > > ./src/wcg/configure.ac
>> > > ./src/xml/txpp/lib/configure.ac
>> > > ./tests/configure.ac
>> > >
>> > > I think what's happening is that when I run build.sh, configure is
>> > picking
>> > > up the configure.ac files in the different directories. I don't want
>> to
>> > > change the configure.ac files for all these directories everytime I
>> want
>> > > to
>> > > build on a new platform so, what can we do? Why do we have all these
>> > > configure.ac files ?  Why not just have the one root configure.ac
>> file
>> > > that
>>
> === message truncated ===
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Friends.  Fun.  Try the all-new Yahoo! Messenger.
> http://messenger.yahoo.com/
>
>


Re: configure.ac

Posted by Samisa Abeysinghe <sa...@yahoo.com>.
Hi John,
    I thnk you just need 4 configure.ac files
1. ./configure.ac                                - the top level
2. ./samples/client/configure.ac                       - samples
3. ./samples/server/configure.ac                       - samples
4. ./tests/configure.ac                          - tests

However, there is no argument that even 4 is too much.
As an immediate solution what could be done it to include 2, 3 and 4 above in 1.

This way it will come down to a single configure.ac.

Thanks,
Samisa..

--- John Hawkins <HA...@uk.ibm.com> wrote:
> 
> 
> 
> 
> Hi Kenneth,
> 
> I appreciate that the end-user has no issues with this -  I'm coming from
> the viewpoint of having to compile Axis C on X different platforms (where
> X> 5 let's put it that way). Therefore I don't want to make 8*5 changes
> (plus any other things I have to do) on every platform . I thought the
> point of libtools was that they encapsulated platform specific issues into
> their structure?
> 
> My points still hold about the fact that we have 8 configure files for a
> not very big project. When, in my humble opinion, we could either have one
> (src)or a maximum of three. (src, samples, tests). In my opinion, and
> having worked with many builds, there is no reason to have this level of
> complexity or number of makefiles.
> 
> John Hawkins
> 
> 
> 
> 
>                                                                            
>              Kenneth Chiu                                                  
>              <chiuk@cs.indiana                                             
>              .edu>                                                      To 
>                                        Apache AXIS C Developers List       
>              11/06/2004 12:09          <ax...@ws.apache.org>          
>                                                                         cc 
>                                                                            
>              Please respond to                                     Subject 
>               "Apache AXIS C           Re: configure.ac                    
>              Developers List"                                              
>                                                                            
>                                                                            
>                                                                            
>                                                                            
>                                                                            
> 
> 
> 
> 
> The usual practice for something like this is that you write
> new macros and put them in a common place, then use some way
> to include them.  (There are a number of ways.)
> 
> Do 'info aclocal' and look at the sections on macros.
> 
> Normally, you don't ship the configure.ac's anyway, so a
> little bit of complexity during the autoconf process doesn't
> affect the end-user.
> 
> Just in case you don't know about already, there is an
> on-line autotools book:
> 
>     http://sources.redhat.com/autobook/autobook/autobook_toc.html
> 
> On Fri, 11 Jun 2004, John Hawkins wrote:
> 
> >
> >
> >
> >
> > OK, that's a start. I understand why we need a make file for each tree
> > (kinda)
> >
> > However, I still need to change 8 configure.ac files everytime I want to
> > port to AIX (or another platform with issues). That's not very portable.
> >
> > Looking at my original listing I see the following configure files
> (minus
> > the ones you've just removed)
> >
> >
> > > ./configure.ac                                - the top level
> > > ./samples/client/configure.ac                       - samples
> > > ./samples/client/testHandler/configure.ac                 - samples
> > > ./samples/server/configure.ac                       - samples
> > > ./src/server/handlers/global/testhandler1/configure.ac    - handler
> > samples or tests?
> > > ./src/server/handlers/transport/testhandler2/configure.ac - handlers
> > samples or tests?
> > > ./src/wcg/configure.ac                              - what is this ?
> > > ./src/xml/txpp/lib/configure.ac                     - what is this?
> > > ./tests/configure.ac                          - tests
> >
> > Few observations -
> > Why do we have lots of different sample files - Surely we just need one
> for
> > the samples tree
> > Samples and/or tests seem be scattered throughout the code base?
> >
> > I also need to understand why we don't have a more simple structure with
> > say a configure file for the following :
> > src
> > tests
> > samples
> >
> > Alternatively we could have one big tree structure with say
> >
> > src
> > src/samples
> > src/tests
> >
> > then I could have one configure.ac file at the top level?
> > If I wanted to build "all" I could or I could pick and choose which I
> > wanted.
> >
> > That would seem more logical to me and far more easy to maintain and port
> ?
> >
> > I appreciate the code has "grown up" but I don't think that I'm way out
> of
> > line here am I?
> >
> > what do people think?
> >
> >
> >
> >
> > John Hawkins
> >
> >
> >
> >
> >
> >              damitha@opensourc
> >              e.lk
> >
> To
> >              11/06/2004 08:54          "Apache AXIS C Developers List"
> >                                        <ax...@ws.apache.org>
> >
> cc
> >              Please respond to
> >               "Apache AXIS C
> Subject
> >              Developers List"          Re: configure.ac
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi John,
> >    Actuall following file are not needed. I removed them
> >    ./samples/server/echoStringHeaderHandler/configure.ac
> >   ./samples/server/interoptests/doclitbase/configure.ac
> >   ./samples/server/interoptests/doclitgroupB/configure.ac
> >
> > 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.
> >
> > damitha
> > >
> > >
> > > Hi Folks,
> > >
> > > Trying to get the latest code building on AIX.
> > >
> > > The compiler I'm using is not understanding the CPPFlags but I know
> what
> > > to
> > > set them to. My question is - if I change configure.ac in the c
> directory
> > > why are there other configure.ac's in other directories (listed below)
> ->
> > >
> > > /home/hawkeye/axis12
> > > # find . -name configure.ac -print
> > > ./configure.ac
> > > ./samples/client/configure.ac
> > > ./samples/client/testHandler/configure.ac
> > > ./samples/server/configure.ac
> > > ./samples/server/echoStringHeaderHandler/configure.ac
> > > ./samples/server/interoptests/doclitbase/configure.ac
> > > ./samples/server/interoptests/doclitgroupB/configure.ac
> > > ./src/server/handlers/global/testhandler1/configure.ac
> > > ./src/server/handlers/transport/testhandler2/configure.ac
> > > ./src/wcg/configure.ac
> > > ./src/xml/txpp/lib/configure.ac
> > > ./tests/configure.ac
> > >
> > > I think what's happening is that when I run build.sh, configure is
> > picking
> > > up the configure.ac files in the different directories. I don't want to
> > > change the configure.ac files for all these directories everytime I
> want
> > > to
> > > build on a new platform so, what can we do? Why do we have all these
> > > configure.ac files ?  Why not just have the one root configure.ac file
> > > that
> 
=== message truncated ===



	
		
__________________________________
Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/ 

Re: configure.ac

Posted by John Hawkins <HA...@uk.ibm.com>.



Hi Kenneth,

I appreciate that the end-user has no issues with this -  I'm coming from
the viewpoint of having to compile Axis C on X different platforms (where
X> 5 let's put it that way). Therefore I don't want to make 8*5 changes
(plus any other things I have to do) on every platform . I thought the
point of libtools was that they encapsulated platform specific issues into
their structure?

My points still hold about the fact that we have 8 configure files for a
not very big project. When, in my humble opinion, we could either have one
(src)or a maximum of three. (src, samples, tests). In my opinion, and
having worked with many builds, there is no reason to have this level of
complexity or number of makefiles.

John Hawkins




                                                                           
             Kenneth Chiu                                                  
             <chiuk@cs.indiana                                             
             .edu>                                                      To 
                                       Apache AXIS C Developers List       
             11/06/2004 12:09          <ax...@ws.apache.org>          
                                                                        cc 
                                                                           
             Please respond to                                     Subject 
              "Apache AXIS C           Re: configure.ac                    
             Developers List"                                              
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




The usual practice for something like this is that you write
new macros and put them in a common place, then use some way
to include them.  (There are a number of ways.)

Do 'info aclocal' and look at the sections on macros.

Normally, you don't ship the configure.ac's anyway, so a
little bit of complexity during the autoconf process doesn't
affect the end-user.

Just in case you don't know about already, there is an
on-line autotools book:

    http://sources.redhat.com/autobook/autobook/autobook_toc.html

On Fri, 11 Jun 2004, John Hawkins wrote:

>
>
>
>
> OK, that's a start. I understand why we need a make file for each tree
> (kinda)
>
> However, I still need to change 8 configure.ac files everytime I want to
> port to AIX (or another platform with issues). That's not very portable.
>
> Looking at my original listing I see the following configure files
(minus
> the ones you've just removed)
>
>
> > ./configure.ac                                - the top level
> > ./samples/client/configure.ac                       - samples
> > ./samples/client/testHandler/configure.ac                 - samples
> > ./samples/server/configure.ac                       - samples
> > ./src/server/handlers/global/testhandler1/configure.ac    - handler
> samples or tests?
> > ./src/server/handlers/transport/testhandler2/configure.ac - handlers
> samples or tests?
> > ./src/wcg/configure.ac                              - what is this ?
> > ./src/xml/txpp/lib/configure.ac                     - what is this?
> > ./tests/configure.ac                          - tests
>
> Few observations -
> Why do we have lots of different sample files - Surely we just need one
for
> the samples tree
> Samples and/or tests seem be scattered throughout the code base?
>
> I also need to understand why we don't have a more simple structure with
> say a configure file for the following :
> src
> tests
> samples
>
> Alternatively we could have one big tree structure with say
>
> src
> src/samples
> src/tests
>
> then I could have one configure.ac file at the top level?
> If I wanted to build "all" I could or I could pick and choose which I
> wanted.
>
> That would seem more logical to me and far more easy to maintain and port
?
>
> I appreciate the code has "grown up" but I don't think that I'm way out
of
> line here am I?
>
> what do people think?
>
>
>
>
> John Hawkins
>
>
>
>
>
>              damitha@opensourc
>              e.lk
>
To
>              11/06/2004 08:54          "Apache AXIS C Developers List"
>                                        <ax...@ws.apache.org>
>
cc
>              Please respond to
>               "Apache AXIS C
Subject
>              Developers List"          Re: configure.ac
>
>
>
>
>
>
>
>
>
>
> Hi John,
>    Actuall following file are not needed. I removed them
>    ./samples/server/echoStringHeaderHandler/configure.ac
>   ./samples/server/interoptests/doclitbase/configure.ac
>   ./samples/server/interoptests/doclitgroupB/configure.ac
>
> 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.
>
> damitha
> >
> >
> > Hi Folks,
> >
> > Trying to get the latest code building on AIX.
> >
> > The compiler I'm using is not understanding the CPPFlags but I know
what
> > to
> > set them to. My question is - if I change configure.ac in the c
directory
> > why are there other configure.ac's in other directories (listed below)
->
> >
> > /home/hawkeye/axis12
> > # find . -name configure.ac -print
> > ./configure.ac
> > ./samples/client/configure.ac
> > ./samples/client/testHandler/configure.ac
> > ./samples/server/configure.ac
> > ./samples/server/echoStringHeaderHandler/configure.ac
> > ./samples/server/interoptests/doclitbase/configure.ac
> > ./samples/server/interoptests/doclitgroupB/configure.ac
> > ./src/server/handlers/global/testhandler1/configure.ac
> > ./src/server/handlers/transport/testhandler2/configure.ac
> > ./src/wcg/configure.ac
> > ./src/xml/txpp/lib/configure.ac
> > ./tests/configure.ac
> >
> > I think what's happening is that when I run build.sh, configure is
> picking
> > up the configure.ac files in the different directories. I don't want to
> > change the configure.ac files for all these directories everytime I
want
> > to
> > build on a new platform so, what can we do? Why do we have all these
> > configure.ac files ?  Why not just have the one root configure.ac file
> > that
> > holds the flags for that platform?
> >
> > thanks for any help (Ignorance plays a large part in my questions so
bare
> > with me :-)
> >
> > John Hawkins
> >
> >
> >
>
>
>



Re: configure.ac

Posted by Kenneth Chiu <ch...@cs.indiana.edu>.
The usual practice for something like this is that you write
new macros and put them in a common place, then use some way
to include them.  (There are a number of ways.)

Do 'info aclocal' and look at the sections on macros.

Normally, you don't ship the configure.ac's anyway, so a
little bit of complexity during the autoconf process doesn't
affect the end-user.

Just in case you don't know about already, there is an
on-line autotools book:

    http://sources.redhat.com/autobook/autobook/autobook_toc.html

On Fri, 11 Jun 2004, John Hawkins wrote:

>
>
>
>
> OK, that's a start. I understand why we need a make file for each tree
> (kinda)
>
> However, I still need to change 8 configure.ac files everytime I want to
> port to AIX (or another platform with issues). That's not very portable.
>
> Looking at my original listing I see the following configure files  (minus
> the ones you've just removed)
>
>
> > ./configure.ac                                - the top level
> > ./samples/client/configure.ac                       - samples
> > ./samples/client/testHandler/configure.ac                 - samples
> > ./samples/server/configure.ac                       - samples
> > ./src/server/handlers/global/testhandler1/configure.ac    - handler
> samples or tests?
> > ./src/server/handlers/transport/testhandler2/configure.ac - handlers
> samples or tests?
> > ./src/wcg/configure.ac                              - what is this ?
> > ./src/xml/txpp/lib/configure.ac                     - what is this?
> > ./tests/configure.ac                          - tests
>
> Few observations -
> Why do we have lots of different sample files - Surely we just need one for
> the samples tree
> Samples and/or tests seem be scattered throughout the code base?
>
> I also need to understand why we don't have a more simple structure with
> say a configure file for the following :
> src
> tests
> samples
>
> Alternatively we could have one big tree structure with say
>
> src
> src/samples
> src/tests
>
> then I could have one configure.ac file at the top level?
> If I wanted to build "all" I could or I could pick and choose which I
> wanted.
>
> That would seem more logical to me and far more easy to maintain and port ?
>
> I appreciate the code has "grown up" but I don't think that I'm way out of
> line here am I?
>
> what do people think?
>
>
>
>
> John Hawkins
>
>
>
>
>
>              damitha@opensourc
>              e.lk
>                                                                         To
>              11/06/2004 08:54          "Apache AXIS C Developers List"
>                                        <ax...@ws.apache.org>
>                                                                         cc
>              Please respond to
>               "Apache AXIS C                                       Subject
>              Developers List"          Re: configure.ac
>
>
>
>
>
>
>
>
>
>
> Hi John,
>    Actuall following file are not needed. I removed them
>    ./samples/server/echoStringHeaderHandler/configure.ac
>   ./samples/server/interoptests/doclitbase/configure.ac
>   ./samples/server/interoptests/doclitgroupB/configure.ac
>
> 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.
>
> damitha
> >
> >
> > Hi Folks,
> >
> > Trying to get the latest code building on AIX.
> >
> > The compiler I'm using is not understanding the CPPFlags but I know what
> > to
> > set them to. My question is - if I change configure.ac in the c directory
> > why are there other configure.ac's in other directories (listed below) ->
> >
> > /home/hawkeye/axis12
> > # find . -name configure.ac -print
> > ./configure.ac
> > ./samples/client/configure.ac
> > ./samples/client/testHandler/configure.ac
> > ./samples/server/configure.ac
> > ./samples/server/echoStringHeaderHandler/configure.ac
> > ./samples/server/interoptests/doclitbase/configure.ac
> > ./samples/server/interoptests/doclitgroupB/configure.ac
> > ./src/server/handlers/global/testhandler1/configure.ac
> > ./src/server/handlers/transport/testhandler2/configure.ac
> > ./src/wcg/configure.ac
> > ./src/xml/txpp/lib/configure.ac
> > ./tests/configure.ac
> >
> > I think what's happening is that when I run build.sh, configure is
> picking
> > up the configure.ac files in the different directories. I don't want to
> > change the configure.ac files for all these directories everytime I want
> > to
> > build on a new platform so, what can we do? Why do we have all these
> > configure.ac files ?  Why not just have the one root configure.ac file
> > that
> > holds the flags for that platform?
> >
> > thanks for any help (Ignorance plays a large part in my questions so bare
> > with me :-)
> >
> > John Hawkins
> >
> >
> >
>
>
>

Re: configure.ac

Posted by John Hawkins <HA...@uk.ibm.com>.



OK, that's a start. I understand why we need a make file for each tree
(kinda)

However, I still need to change 8 configure.ac files everytime I want to
port to AIX (or another platform with issues). That's not very portable.

Looking at my original listing I see the following configure files  (minus
the ones you've just removed)


> ./configure.ac                                - the top level
> ./samples/client/configure.ac                       - samples
> ./samples/client/testHandler/configure.ac                 - samples
> ./samples/server/configure.ac                       - samples
> ./src/server/handlers/global/testhandler1/configure.ac    - handler
samples or tests?
> ./src/server/handlers/transport/testhandler2/configure.ac - handlers
samples or tests?
> ./src/wcg/configure.ac                              - what is this ?
> ./src/xml/txpp/lib/configure.ac                     - what is this?
> ./tests/configure.ac                          - tests

Few observations -
Why do we have lots of different sample files - Surely we just need one for
the samples tree
Samples and/or tests seem be scattered throughout the code base?

I also need to understand why we don't have a more simple structure with
say a configure file for the following :
src
tests
samples

Alternatively we could have one big tree structure with say

src
src/samples
src/tests

then I could have one configure.ac file at the top level?
If I wanted to build "all" I could or I could pick and choose which I
wanted.

That would seem more logical to me and far more easy to maintain and port ?

I appreciate the code has "grown up" but I don't think that I'm way out of
line here am I?

what do people think?




John Hawkins




                                                                           
             damitha@opensourc                                             
             e.lk                                                          
                                                                        To 
             11/06/2004 08:54          "Apache AXIS C Developers List"     
                                       <ax...@ws.apache.org>          
                                                                        cc 
             Please respond to                                             
              "Apache AXIS C                                       Subject 
             Developers List"          Re: configure.ac                    
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




Hi John,
   Actuall following file are not needed. I removed them
   ./samples/server/echoStringHeaderHandler/configure.ac
  ./samples/server/interoptests/doclitbase/configure.ac
  ./samples/server/interoptests/doclitgroupB/configure.ac

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.

damitha
>
>
> Hi Folks,
>
> Trying to get the latest code building on AIX.
>
> The compiler I'm using is not understanding the CPPFlags but I know what
> to
> set them to. My question is - if I change configure.ac in the c directory
> why are there other configure.ac's in other directories (listed below) ->
>
> /home/hawkeye/axis12
> # find . -name configure.ac -print
> ./configure.ac
> ./samples/client/configure.ac
> ./samples/client/testHandler/configure.ac
> ./samples/server/configure.ac
> ./samples/server/echoStringHeaderHandler/configure.ac
> ./samples/server/interoptests/doclitbase/configure.ac
> ./samples/server/interoptests/doclitgroupB/configure.ac
> ./src/server/handlers/global/testhandler1/configure.ac
> ./src/server/handlers/transport/testhandler2/configure.ac
> ./src/wcg/configure.ac
> ./src/xml/txpp/lib/configure.ac
> ./tests/configure.ac
>
> I think what's happening is that when I run build.sh, configure is
picking
> up the configure.ac files in the different directories. I don't want to
> change the configure.ac files for all these directories everytime I want
> to
> build on a new platform so, what can we do? Why do we have all these
> configure.ac files ?  Why not just have the one root configure.ac file
> that
> holds the flags for that platform?
>
> thanks for any help (Ignorance plays a large part in my questions so bare
> with me :-)
>
> John Hawkins
>
>
>




Re: configure.ac

Posted by da...@opensource.lk.
Hi John,
   Actuall following file are not needed. I removed them
   ./samples/server/echoStringHeaderHandler/configure.ac
  ./samples/server/interoptests/doclitbase/configure.ac
  ./samples/server/interoptests/doclitgroupB/configure.ac

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.

damitha
>
>
> Hi Folks,
>
> Trying to get the latest code building on AIX.
>
> The compiler I'm using is not understanding the CPPFlags but I know what
> to
> set them to. My question is - if I change configure.ac in the c directory
> why are there other configure.ac's in other directories (listed below) ->
>
> /home/hawkeye/axis12
> # find . -name configure.ac -print
> ./configure.ac
> ./samples/client/configure.ac
> ./samples/client/testHandler/configure.ac
> ./samples/server/configure.ac
> ./samples/server/echoStringHeaderHandler/configure.ac
> ./samples/server/interoptests/doclitbase/configure.ac
> ./samples/server/interoptests/doclitgroupB/configure.ac
> ./src/server/handlers/global/testhandler1/configure.ac
> ./src/server/handlers/transport/testhandler2/configure.ac
> ./src/wcg/configure.ac
> ./src/xml/txpp/lib/configure.ac
> ./tests/configure.ac
>
> I think what's happening is that when I run build.sh, configure is picking
> up the configure.ac files in the different directories. I don't want to
> change the configure.ac files for all these directories everytime I want
> to
> build on a new platform so, what can we do? Why do we have all these
> configure.ac files ?  Why not just have the one root configure.ac file
> that
> holds the flags for that platform?
>
> thanks for any help (Ignorance plays a large part in my questions so bare
> with me :-)
>
> John Hawkins
>
>
>