premake / premake/premake-core

Xcode does not support custom build commands

Open
#940 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

It seems the Xcode module does not handle custom build commands. We just switched to using them for 0 A.D.'s build system for the tests, and the Xcode test project doesn't work.

This is apparently the subject of a "forgotten" PR.

This can be tested by building 0 A.D., but the following "minimal" example works too:

workspace "Example"
	configurations { "Release" }
	platforms { "macOS" }
	location ("workspaces/")
	language "C++"
	targetdir ("build/output")
	objdir ("build/obj")
	nativewchar "Off"
	buildoptions { "-Wall", "-Wextra" }

project "Example"
	kind "ConsoleApp"

	files { "main.cpp" }

	filter "files:*.cpp"
		buildmessage 'Doing stuff'
		buildcommands {
			'touch somefile.cpp'
		}

		buildoutputs { 'somefile.cpp' }

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 reviewing the forgotten premake-xcode PR #39 and reproducing the provided minimal workspace with Xcode. Compare its custom buildmessage, buildcommands, and buildoutputs behavior with the failing 0 A.D. test project; done means the generated Xcode project builds and runs the custom command correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, macos
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.