openframeworks / openframeworks/openFrameworks
projectGenerator update doesn't respect existing project settings
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
On 'update', PG should respect existing custom include paths, source files, linker flags and project options (such as optimization settings).
OR
Xcode project should read and respect OTHER_LDFLAGS and HEADER_SEARCH_PATHS, and add OTHER_CFLAGS from Project.xcconfig; projectGenerator should leave these settings alone unless it figures out they need to be adjusted (this is probably going to be difficult).
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 tracing the projectGenerator update flow and how the Xcode project reads Project.xcconfig. Compare existing custom include paths, source files, linker flags, project options, OTHER_LDFLAGS, HEADER_SEARCH_PATHS, and OTHER_CFLAGS before defining the expected preservation behavior. Done means updates leave existing settings intact unless adjustment is necessary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100