Incidentally, no longer run Dynare++ unit tests, since they are intricated in
the Dynare++ build system. If we finally decide not to drop the Dynare++
codebase for our MEX files, then we should probably find a way to build and run
them again.
Ref. #1825
This was introduced in Gitlab 13.0.
By the way, this ensures that test artifacts which are deep in the directory
hierarchy (such as those for the MoM tooblox) are also taken into account.
– preprocessor binary renamed to dynare-preprocessor
— the preprocessor binary is now installed under a preprocessor/ top-level directory
— a backward-compatibility symlink is still provided under
matlab/preprocessor64/dynare_m
— the make install rule now install PDF and HTML documentation when those have
been built
Closes: #1728
It is thus no longer needed to pass the MATLAB_VERSION option to the configure
script when compiling from source.
(cherry picked from commit a69d598b5f)
In particular, this allows us to split the “test” and “pkg” stages, without
increasing the execution time.
(manually cherry picked from commit ac59b22015)
— This is consistent with the fact that we hardcode the old MATLAB version
— This ensures better homogeneity across runners (in theory, it could be
possible that different runners have different “matlab” symlinks)
— This allows easier customization in personal repositories
The copy of MathJax that we were embedding was not source code, because it
contained minified Javascript. In particular, this is a problem for the
official Debian package.
We now strip the copy. Users compiling the HTML manual from the source tarball
will therefore get MathJax from a CDN (this is the default behaviour of
Sphinx).
It is not possible to use --disable-matlab and --disable-octave, because
otherwise `make dist` does not properly recurse.
By the way, factorize the computation of the path and version of the default
MATLAB installation.
In particular, if either MATLAB or Octave is missing, one needs to pass either
--disable-matlab or --disable-octave.
Moreover, several new configure flags have been introduced for disabling some
components:
--disable-doc
--disable-dynare++
--disable-mex-dynare++
--disable-mex-ms-sbvar
--disable-mex-kalman-steady-state
This is not strictly needed since currently there is no submodule within a
submodule in Dynare. However, this is useful for the Enterprise
version (dseries has a matlab-fame-io submodule there). Moreover, this will
prevent bad surprises in the future should we introduce such a 2nd-level
submodule.
Sébastien Villemot
Stéphane Adjemian (Odysseus)