premake / premake/premake-core
Problems with selective file level optimizations and debug symbols on
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 654
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 13
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating m.clCompileFiles and m.debugInformationFormat in the Premake source. Reproduce the Visual Studio build with project-level Symbols and file-level Optimize settings, then verify that the generated command line no longer combines incompatible /ZI and /O2 options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, lua
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100