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

List:       axis-c-dev
Subject:    Re: configure.ac
From:       Kenneth Chiu <chiuk () cs ! indiana ! edu>
Date:       2004-06-11 20:11:47
Message-ID: Pine.GSO.4.58.0406111454320.8660 () mishrak ! extreme ! indiana ! edu
[Download RAW message or body]

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          <axis-c-dev@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"
> >                                        <axis-c-dev@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
> > >
> > >
> > >
> >
> >
> >
>
>
[prev in list] [next in list] [prev in thread] [next in thread]