premake / premake/premake-core
How to handle conflicting API (in external modules)?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 654
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 13
Description
What's your question?
I test external modules, I put generators in premake5-system.lua
I have one project which uses one module with "conflicting" api
same name, (and even same definition) leading to errors.
Which is the proper way to handle that?
For actual case, it is premake-qt and premake-qmake with api qtmodules.
Anything else we should know?
From https://github.com/dcourtois/premake-qt/pull/33
The proper way to fixing that would be to have the ability to create addon namespaces, but that's something that needs to be solved in Premake-core.
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 with the external-module setup in premake5-system.lua and compare how premake-qt and premake-qmake expose the conflicting qtmodules API. Read the context from premake-qt pull request 33 and determine the intended core-level approach for handling addon namespaces. Done means the proper behavior and required Premake-core change are specified clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100