openframeworks / openframeworks/openFrameworks
"clean" on osx projects always cleans the openframeworks lib (xcode 6.3.2)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
on xcode 6.3.2, osx 10.11.1
clean seems to delete openframeworks lib as well as the project -- there's not easy way I can see to just clean for the scheme (ie, just the src of the project).
this seems to have always been the case, but now it's much more painful because we are compiling for 32 bit and 64 bit at once, it feels like it takes forever if you need to clean a project. when updating 0.8.4 projects to 0.9.0 it seems to help to clean them... (in this case, the older .app is conflicting a bit with rsync, etc)
this is probably part of a larger conversation about a better way to include the OF lib as a dependency -- it feels like there might be a better way to do this?
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 reproducing the clean behavior in Xcode 6.3.2 on OS X 10.11.1, then inspect the project’s scheme and dependency/build settings to determine why the openFrameworks library is removed. Done means a scheme clean removes the project’s build output without unnecessarily deleting the openFrameworks library.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, macos
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100