premake / premake/premake-core
why target tokens are not use otherwhere.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 654
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 13
Description
Why these Tokens
target.abspath
target.basename
target.bundlename
target.bundlepath
target.directory
target.extension
target.name
target.prefix
target.relpath
target.suffix
not use in postbuildcommands.
I will copy target and it's map file and pdb file to other path, pack those send to FTP server.
it is base on target name and path, but these tokens are not invalid in postbuildcommands.
i use $(TargetPath) $(TargetDir) VS support. others, use name directly. that is not good.
i think it is valuable in postbuildcommands
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 postbuildcommands expands target tokens and compare that path with the listed target.* tokens. Confirm the requested target values work in postbuildcommands, including the paths and names needed for copying and packaging, then verify the generated commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, lua
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100