premake/premake-core

Problems with selective file level optimizations and debug symbols on

Open

#116 opened on Jun 16, 2015

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)C (651 forks)auto 404
enhancementhelp wantedvs20xx

Repository metrics

Stars
 (3,621 stars)
PR merge metrics
 (PR metrics pending)

Description

If you define (for instance) this at the project level

flags { "Symbols" }

But then define this with a filter on specific source files

flags { "Optimize" }
optimize "Speed"

It is possible to see this error when you build in visual studio.

    cl : Command line error D8016: '/ZI' and '/O2' command-line options are incompatible

The bug seems to be the fact that the function m.clCompileFiles does not call m.debugInformationFormat() at the file level if necessary (if optimization is switched on for specific files).

Contributor guide

Research direction
Inspect the function m.clCompileFiles in Premake's source to understand how file level optimization flags are applied. Add a call to m.debugInformationFormat() when optimization is enabled for a specific file to ensure debug symbol format is compatible.
Tech stack
lua
Domain
build system
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Lua
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70