Building trunk, should I run ffc or expect the build script to do so?

Asked by Charles

After pulling changes I had to run ffc -f split -l dolfin *.ufl in dolfin/ale, should I expect the build script to do this for me?

Question information

Language:
English Edit question
Status:
Solved
For:
DOLFIN Edit question
Assignee:
No assignee Edit question
Solved by:
Charles
Solved:
Last query:
Last reply:
Revision history for this message
Charles (rodbourn) said :
#1

https://bugs.launchpad.net/dolfin/+bug/1158504

Anders Logg (logg) wrote on 2013-03-21: Re: [Bug 1158504] [NEW] docstrings.i missing #1
See the FEniCS mailing list. We are preparing a conversion to Git and
at the same time deleting generated files (both Poisson.h etc and
docstring files). It will take a day or two before this settles as we
are awaiting more comments from developers.

You should run

  cmake/scripts/generate-all

and ideally this should be handled in a user-friendly way via the
build system.

[...]
On Thu, Mar 21, 2013 at 08:31:19PM -0000, Mikael Mortensen wrote:
[...]