openframeworks / openframeworks/openFrameworks
Allow path in addons.make outside of $(OF_PATH)/addons
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
(Spun off from a question on the forum Project encapsulation and addons.make referencing addons not in $(OF_PATH)/addons)
It would be great if addons.make were flexible enough to handle paths to addons, in addition to the usual addon name mapping to $(OF_PATH)/addons.
In an effort to fully encapsulate a project and its dependencies, I have an addons directory within my project and it would be fantastic if I didn't have to duplicate all the great addon make machinery that handles addon-specific configuration in addon_config.mk as well as the include / source path stuff.
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 how addons.make maps addon names to $(OF_PATH)/addons and how addon_config.mk supplies addon-specific configuration, include paths, and source paths. The issue is done when an addons.make entry can reference an addon directory inside a project or another external path without duplicating that make machinery.
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
- Mostly clear
- Newbie friendliness
- 32/100