Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • dynare dynare
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 108
    • Issues 108
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Dynare
  • dynaredynare
  • Issues
  • #1483
Closed
Open
Created Jul 24, 2017 by Houtan Bastani@houtanbDeveloper

if Dynare++ will not be built, do not build mex files that depend on it

mex/build/matlab/configure.ac does not account for the case when makefiles are not created for dynare++ by the main configure script. Hence, libdynare++ and gensylv will still be built, causing an error. See #1482 (closed).

Easy solution: test for BLAS, LAPACK, and MatIO. don't build libdynare++, gensylv, k_order_perturbation, or dynare_simul_ if one of these libraries is not found (same test that we implement for building Dynare++ in the main config file.

Another solution would be to pass the value of BUILD_DYNAREPLUSPLUS to AC_CONFIG_SUBDIRS([mex/build/matlab]) in configure.ac

Assignee
Assign to
Time tracking