Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • ExaHyPE-Engine ExaHyPE-Engine
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 68
    • Issues 68
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

9.2.2023: Due to updates GitLab will be unavailable for some minutes between 9:00 and 11:00.

  • ExaHyPEExaHyPE
  • ExaHyPE-EngineExaHyPE-Engine
  • Issues
  • #245
Closed
Open
Issue created Sep 01, 2018 by Sven Köppel@svenk2Owner

Toolkit2: Allow users to share binaries, move them accross computers, etc.

The new ExaHyPE Parser C++ infrastructure currently does a suprocess to call the Toolkit in order to convert old-fashioned specification files. To do so, the call to Toolkit/toolkit.sh is hardcoded, including the path.

This raises problems in certain use cases:

  • The user shares his Executable to another user on the system/cluster but does not make the access permissions correctly for the Toolkit
  • The user copies only the Executable to another machine but not the overall Code (especially not the Toolkit code)
  • The user renames the path to his installation (probably when cleaning up his home directory) but wants to keep an ExaHyPE build working (obviously this is not possible)

We have no solution for all these use cases, but we should include checks in the C++ code to deal with them:

  • Check whether Path/to/Toolkit/toolkit.sh exists, is readable and executable
Assignee
Assign to
Time tracking

LRZ Homepage | Datenschutz | Dokumentation und Betriebsbedingungen | Impressum