premake / premake/premake-core

Default Generator

Open
#1,479 1 comment 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?
I automatically call Premake on several projects, and currently I have the generator hardcoded into the script.
Problem is I want to use a different generator per platform, or switch to a different generator, or use the latest Visual Studio generator.

What might be a solution?
two part:

  1. option to set a system wide default generator that will be used when no generator is explicitly specified.
  2. "vs-latest" generator option that automatically finds and uses the latest Vistual Studio version that's installed.

What other alternatives have you already considered?
might be possible to do dirty hacks like using environment variables.

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 tracing how Premake chooses a generator when none is supplied and how installed Visual Studio versions are discovered. Compare the requested system-wide default and "vs-latest" behaviors with existing generator handling, then define tests that show both options work across platforms.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, lua
Domain
build-system
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.