premake / premake/premake-core

Add better --version information

Open
#2,445 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
C
Stars
3.6k
Forks
654
Avg merge
1d 1h
Merged PRs (30d)
13

Description

What problem will this solve?
According to the output from --version I'm currently using 5.0.0-dev. But that doesn't tell me exactly which commit my executable was built from. Having at least a timestamp of when the executable was built would enable me to see at a glance whether I might be missing some important fix or feature.

What might be a solution?
Including the executable build time (and commit number for development builds) would give a clearer indication of how old (or new) a Premake executable is.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the existing --version output and the executable build metadata in the Premake source and build configuration. Confirm the desired behavior for development versus released builds, then verify that --version shows the build time and a commit identifier where applicable.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.