Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C clean-ide
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • 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
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • clean-and-itasks
  • clean-ide
  • Merge requests
  • !23

Merged
Created Oct 06, 2019 by Camil Staps@cstapsContributor

Use separate link options file for the bytecode linker to avoid long command lines

  • Overview 2
  • Commits 1
  • Pipelines 2
  • Changes 1

With large projects and long paths, the call to ByteCodeLinker.exe (which needs all .bc files) could become too large for the Windows command line limits (32768 chars). In https://gitlab.science.ru.nl/clean-and-itasks/abc-interpreter/merge_requests/116 I added a -f option to the linker to be able to read input files from a separate file; this patch uses that in cpm/the IDE.

!22 (merged) is still useful to give meaningful error messages should the same problem occur elsewhere in the future.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: bclink-options-file