openframeworks / openframeworks/projectGenerator
PG converts all paths into relative paths.
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 90
- Forks
- 79
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 5
Description
It appears that the PG currently converts all paths indiscriminately into relative paths.
However, I believe absolute paths should be excluded from this behavior.
A concrete example would be addons that depend on libraries installed system-wide, such as those provided via Homebrew. In such cases, converting these paths to relative ones can cause issues.
At the moment, I am exploring ways to run build tests when tools like Claude Code use git worktree. Using symlinks seems sufficient for handling libs and addons, but if paths inside the xcodeproj are automatically rewritten in this way, they inevitably become invalid due to path mismatches.
Contributor guide
No contributing guide indexed for this repository
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 at the project-generator path conversion that rewrites paths inside the xcodeproj, using the reported system-wide Homebrew library and git worktree/symlink scenario as reproduction context. Verify that absolute paths remain unchanged while relative paths retain current behavior, and confirm the generated xcodeproj paths work in the build tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100