dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

On Tue, Jan 31, 2006 at 04:57:34PM +0100, Johan Jansson wrote:
> On Tue, Jan 31, 2006 at 09:38:45AM -0600, Anders Logg wrote:
> > To keep the installation process as simple as possible (configure +
> > make + make install), it seems logical to either break out PyDOLFIN as
> > a separate package, or to compile PyDOLFIN against the source tree
> > rather than an installed version, so it can be compiled during make
> > and installed during make install. What do you think?
> > 
> > /Anders
> > 
> 
> I think the best thing to do would be to compile PyDOLFIN agianst the
> source tree. Other things have been higher on the priority list, but
> now it's starting to become important when users are actually
> installing it.
> 
> I don't think it's good to have PyDOLFIN as a separate package, since
> it depends on the entire DOLFIN interface. So any interface change
> aywhere could break PyDOLFIN. It's better to keep the same versioning
> for both DOLFIN and PyDOLFIN.
> 
>   Johan

I agree. Let's keep it in the same package and compile against the
source.

It should be possible to get all the required flags from
autotools. Everything you need should be in @DOLFIN_CFLAGS@ exported
by configure to each Makefile.am.

/Anders