ffc team mailing list archive
-
ffc team
-
Mailing list archive
-
Message #01825
Re: ffc define header error
On Fri, Sep 26, 2008 at 10:25:04PM +0100, Garth N. Wells wrote:
>
>
> Kristian Oelgaard wrote:
> > Quoting Andy Ray Terrel <aterrel@xxxxxxxxxxxx>:
> >
> >> Could we get ffc to be smarter about the header defines. For example
> >> if I compile a form from a different directory than the form file is
> >> in I get a "/" in the name.
> >>
> >> For example:
> >>
> >> #ifndef __NORMS/P4VECDIVL2_H
> >> #define __NORMS/P4VECDIVL2_H
> >>
> >> But I would prefer:
> >>
> >> #ifndef __P4VECDIVL_H
> >> #define __P4VECDIVL2_H
> >
> > I've implemented this solution, the output from FFC will be located in the same
> > directory as the form file i.e.,
> >
> > ffc foo/bar/Poisson.form --> foo/bar/Poisson.h
> >
>
> I think that
>
> ffc foo/bar/Poisson.form --> ./Poisson.h
>
> is what a user would expect.
>
> Garth
I agree. In particular, both latex and gcc work like this.
--
Anders
Attachment:
signature.asc
Description: Digital signature
Follow ups
References