openframeworks / openframeworks/openFrameworks
Optimisation consistency
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
Continuation of http://forum.openframeworks.cc/index.php/topic,9095.msg42378.html#new
NOTE: Things may have changed as the projects I'm using are all created using the older creation tools.
Can somebody up to date please check?
Currently XCode's default project setting is /O2 for debug projects
whilst Visual Studio's is /O0
/O0 generally makes the most sense for debug mode as it allows for effective program flow and variable tracking (because with /O2, lines of code and variables are commonly optimised away).
If we are worried that this will leave default users in a default 'slower state' then perhaps we could make release the default? Then people could be aware that they are selecting debug when they want to actually do some debugging?
But this may have other issues (such as some libraries might not perform as many checks as otherwise?)
it might be worth making users more aware of the 2 options anyway, and then start using them consistently
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
Inspect the XCode and Visual Studio project settings, especially the debug optimization defaults and the older project creation tools mentioned in the issue. Compare the debug and release configurations, then define and verify consistent defaults across the affected platforms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100