dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

I suggest just putting them into the top level directory for
now. Since we're planning to rework the build system with Scons
anyway, we can move all config stuff into a subdirectory then.

Another thing we should do is to use pkg-config. DOLFINs dolfin-config
is modelled after the old gtk-config which later (I think) has
developed into pkg-config. In short, instead of generating a script
dolfin-config, we generate a file dolfin.pc. Check in
/usr/lib/pkgconfig for examples.

/Anders


On Mon, Aug 21, 2006 at 12:18:47PM +0200, Garth N. Wells wrote:
> For configuring some libraries it's useful to use some special scripts 
> to get the compiler options, like in the files petsc.conf and 
> slepc.conf. Should we create a special directory for configure scripts, 
> or would it be ok to put them in the existing directory "scripts"?
> 
> Garth
> 
> DOLFIN wrote:
> >One or more new changesets pushed to the primary DOLFIN repository.
> >A short summary of the last three changesets is included below.
> >
> >changeset:   2141:97f5f8d49f7dac6fac26046f22c68c4aa898ca01
> >tag:         tip
> >user:        "Garth N. Wells <g.n.wells@xxxxxxxxxx>"
> >date:        Mon Aug 21 12:12:49 2006 +0200
> >files:       configure configure.ac 
> >src/kernel/la/PETScEigenvalueSolver.cpp 
> >src/kernel/la/dolfin/PETScEigenvalueSolver.h
> >description:
> >Simplify SLEPc configuration and fix some SLEPc errors.
> >
> >
> >changeset:   2140:58303ab171c2bf43bca3bedee35242ea7db54cc7
> >user:        "Garth N. Wells <g.n.wells@xxxxxxxxxx>"
> >date:        Sun Aug 20 19:48:41 2006 +0200
> >files:       TODO
> >description:
> >Remove more stuff from TODO.
> >
> >
> >changeset:   2139:607c0523e3a86c2157310f45d5f3d251519c50af
> >user:        "Garth N. Wells <g.n.wells@xxxxxxxxxx>"
> >date:        Sun Aug 20 19:08:40 2006 +0200
> >files:       configure petsc.conf
> >description:
> >Small fixes for PETSc flags. Everything seems OK now.
> >
> >
> >-------------------------------------------------------
> >For more details, visit http://www.fenics.org/hg/dolfin
> >_______________________________________________
> >DOLFIN-dev mailing list
> >DOLFIN-dev@xxxxxxxxxx
> >http://www.fenics.org/mailman/listinfo/dolfin-dev
> 
>