Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
codes
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 38
    • Issues 38
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 8
    • Merge Requests 8
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Commits
  • Issue Boards
  • codes
  • codes
  • Issues
  • #22

Closed
Open
Opened Jan 14, 2016 by Jonathan Jenkins@jenkins
  • Report abuse
  • New issue
Report abuse New issue

ross-config always sets -g and and -Wall in CFLAGS

The CODES repos rely on ross-config to provide CFLAGS necessary to compile models that are compatible with the ross installation. These cflags seem to always included -g and -Wall regardless of how ross itself was built.

Ideally these debugging and optimization flags should be left out of ross-config entirely and left up to the project that depends on it, rather than adding possibly conflicting options.

Workaround is to hand edit ross-config after installation to remove unwanted options.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
2
Labels
defect ROSS
Assign labels
  • View project labels
Reference: codes/codes#22