Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • sac2c sac2c
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 395
    • Issues 395
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 24
    • Merge requests 24
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • sac-group
  • sac2csac2c
  • Issues
  • #2237
Closed
Open
Created Oct 22, 2018 by Hans-Nikolai Viessmann@hansOwner

We should build stdlib with installed sac2c

There have been some issues when compiling the stdlib outside of the masterrun. Typically headers give off warnings and errors. This is caused by config.h not being included in as part of the install target.

We have two choices:

  • we include config.h as part of the install target - NTL lib for instance does this
  • we extend the masterrun to install sac2c, and then compile sac2c.

Though we can include config.h, its functions is for when we build the runtime-libraries and often is system specific. Including it in the install target means it also get packages... I'm not sure if this might lead to conflict due to differing system configurations.

Updating the masterrun is fairly straightforward... we can do this first I think.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking