dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

On Fri, Mar 07, 2008 at 08:33:13PM +0100, Ola Skavhaug wrote:
> Anders Logg skrev den 07/03-2008 følgende:
> > On Fri, Mar 07, 2008 at 07:24:23PM +0100, Åsmund Ødegård wrote:
> > > On Fri, Mar 7, 2008 at 7:21 PM, Åsmund Ødegård <aasmund@xxxxxxxxx> wrote:
> > > > On Fri, Mar 7, 2008 at 5:36 PM, Anders Logg <logg@xxxxxxxxx> wrote:
> > > >  [snip]
> > > >
> > > > >  > > This seems a bit strange. 'src' in the root-dir of dolfin is supposed
> > > >  >  > > to be a symlink to 'dolfin'
> > > >  >  > >
> > > >  [snip
> > > >
> > > > >
> > > >  >  Is it necessary to have the src symlink?
> > > >  >
> > > >  >  It hasn't been supported by hg previously (I think) so it may break.
> > > >  >
> > > >
> > > >  Various places in simula_scons, it is assumed that the main sources is
> > > >  located in src/, as the projectname is variable  (dolfin, pycc,....)
> > > >
> > > >  I think this is mostly a convenience, we might go ahe
> > > > (hit send by accident...)
> > > ahead and dig out all locations relying on this, and replace with
> > > env["projectname"] instead.
> > 
> > ok, sounds good.
> > 
> > One thing I wonder is how changes should be made to the build system
> > under scons?
> > 
> > I guess the changes need to take place in the simula­scons repository
> > (wherever that may be located, I forget where it is) and then copied
> > into the DOLFIN repository.
> > 
> > Is it ok to make changes in the scons subdirectory, or should we
> > rather ask you or Johannes to make the changes so that you can
> > synchronize with simula-scons?
> 
> What about constructing a debian package and making dolfin depend on this? I
> know you want dolfin to come with the build/configure system built in, but it
> does provide some additional complications.
> 
> Ola

Will answer later, my laptop's running out of battery right now... :-)

-- 
Anders