[petsc-dev] preparing for PETSc release 3.0.1

[Matthew Knepley]

On Sat, Feb 27, 2010 at 5:44 PM, Satish Balay <balay at mcs.anl.gov> wrote:

> Second issue:
>
> * Its looking for every source file - and attempts to compile it?
>  conftest.c, ex15.c etc.. What does it do to control what sources
>  should be compiled - and what not? [i.e do we specify
>  sourcefile:library dependency?]
>

Currently there is a function checkDir() which can disqualify a given
directory. Otherwise, all C/Fortran files are processed. We can easily
add filters on the files.

I think the right way to add dependencies is to discover them if the tools
are available, and otherwise just rebuild everything.

   Matt


> Satish
> --------------------------------------------------
>
> asterix:/home/balay/tmp/petsc-dev>./config/builder.py
>   Loaded configure to cache: size 210163
> Processing /home/balay/tmp/petsc-dev
> Entering /home/balay/tmp/petsc-dev
> Compiling C files ['conftest.c']
> /home/balay/soft/linux64/mpich2-1.1/bin/mpicc -c
> -I/home/balay/tmp/petsc-dev/asterix64/include
> -I/home/balay/tmp/petsc-dev/include
> -I/home/balay/soft/linux64/mpich2-1.1/include  -fPIC -Wall -Wwrite-strings
> -Wno-strict-aliasing -g3     -D__SDIR__='""' conftest.c
> Archiving files ['conftest.o'] into libpetscfake
> /usr/bin/ar cr /home/balay/tmp/petsc-dev/asterix64/lib/libpetscfake.a
> conftest.o
> Processing /home/balay/tmp/petsc-dev/src
> Entering /home/balay/tmp/petsc-dev/src
> Rejecting /home/balay/tmp/petsc-dev/src/tops because package
> 'PETSC_HAVE_BABEL' is not installed
> Processing /home/balay/tmp/petsc-dev/src/contrib
> Entering /home/balay/tmp/petsc-dev/src/contrib
> Rejecting /home/balay/tmp/petsc-dev/src/contrib/blopex because package
> 'PETSC_HAVE_BLOPEX' is not installed
> Processing /home/balay/tmp/petsc-dev/src/contrib/keyes
> Entering /home/balay/tmp/petsc-dev/src/contrib/keyes
> Compiling C files ['ex15.c']
> /home/balay/soft/linux64/mpich2-1.1/bin/mpicc -c
> -I/home/balay/tmp/petsc-dev/asterix64/include
> -I/home/balay/tmp/petsc-dev/include
> -I/home/balay/soft/linux64/mpich2-1.1/include  -fPIC -Wall -Wwrite-strings
> -Wno-strict-aliasing -g3     -D__SDIR__='"/src/contrib/keyes"' ex15.c
> Archiving files ['ex15.o'] into libpetscfake
> /usr/bin/ar cr /home/balay/tmp/petsc-dev/asterix64/lib/libpetscfake.a
> ex15.o
>
>
> On Sat, 27 Feb 2010, Matthew Knepley wrote:
>
> > 1) builder.py --help :)
> >
> > 2) You give it a root directory to start (default is PETSC_DIR) and it
> does
> > recursive make
> >
> > 3) The current target is libpetscfake.a so I never accidentally blow away
> my
> > install
> >
> >    Matt
> >
> > On Sat, Feb 27, 2010 at 4:44 AM, Satish Balay <balay at mcs.anl.gov> wrote:
> >
> > > Matt,
> > >
> > > Any instructions on how to use/test builder.py?
> > >
> > > Satish
> > >
> > > On Fri, 26 Feb 2010, Matthew Knepley wrote:
> > >
> > > > What do people think about builder.py for the release? I really
> really
> > > want
> > > > a version
> > > > I can use in China.
> > > >
> > > >    Matt
> > > >
> > > > On Thu, Feb 25, 2010 at 2:47 PM, Barry Smith <bsmith at mcs.anl.gov>
> wrote:
> > > >
> > > > >
> > > > >  I'd like to get the next PETSc release out very soon (so we can
> start
> > > > > ripping petsc-dev apart and making it way cooler :-). Please send
> in
> > > any
> > > > > outstanding bug reports and test your applications to make sure the
> > > code is
> > > > > in good shape.
> > > > >
> > > > >   Thanks
> > > > >
> > > > >    Barry
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
> >
>
>


-- 
What most experimenters take for granted before they begin their experiments
is infinitely more interesting than any results to which their experiments
lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100228/3593fb78/attachment.html>