Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • X Xfiles
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 39
    • Issues 39
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • eXlibris
  • Xfiles
  • Issues
  • #25

Closed
Open
Created Dec 18, 2017 by Alexis SALZMAN@asalzmanMaintainer

Keeping boost iostream isolated

Discussion around cmake point out that with some effort (little ?) we may hide boost iostram (used for gzip output) from Xfem interface. That may also be treated as an extra interface in xInterface. In one hand treating it in Xfem correspond to where it is used for now, in the other adding it as an Xinterface gives a way to use it everywhere.

Assignee
Assign to
Time tracking