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 394
    • Issues 394
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 17
    • Merge requests 17
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • sac-group
  • sac2csac2c
  • Issues
  • #2221
Closed
Open
Created Dec 14, 2017 by Artem Shinkarov@temaOwner

[gitlab CI] Build stdlib using sac2c package

Currently, as a part of CI pipeline, we always build stdlib using sac2c binaries directly from the working build directory. The problem with this is that we never test whether resulting package is operational or not. It would be a better idea to extend the pipeline as follows:

  1. Compile sac2c
  2. Create sac2c package
  3. Install sac2c package & build stdlib

This would allow to identify the cases when packages are not fully operational.

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