openframeworks / openframeworks/openFrameworks
oF static lib product named differently when built in Xcode than from make
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
I've run into this a few times and been confused but when building the oF static lib, Xcode uses a different build product name than when building from make 😦
Xcode: libs/openFrameworksCompiled/lib/osx/openFrameworksDebug.a
make: libs/openFrameworksCompiled/lib/osx/libopenFrameworksDebug.a
Should these product names be the same?
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
Compare the Xcode and make build outputs at libs/openFrameworksCompiled/lib/osx/openFrameworksDebug.a and libs/openFrameworksCompiled/lib/osx/libopenFrameworksDebug.a. Start by checking how each build names the static library, then verify that both build paths produce the same product name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, macos
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100