Complex compiler flags for custom buildcommand

[fhoenig]

Taking the example from the docs for luac, how would I add different flags given complex filter combinations like:
filter {"configurations:not Dev-*", "system:windows"}
if those configurations would result in many many repeats of buildcommand.
I've tried (the obviously wrong) concatenating a string for filter scopes which doesn't work like that I know.

What's the suggested way?

Something like:

filter {"configurations:not Dev-*", "system:windows"}
  mycustomflags {"-bla -O -G"}

filter {"configurations:Rel-*", "system:windows"}
  mycustomflags {"-O"}


filter 'files:**.lua'
   -- A message to display while this build step is running (optional)
   buildmessage 'Compiling %{file.relpath}'

   -- One or more commands to run (required)
   buildcommands {
      'luac {%mycustomflags} -o "%{cfg.objdir}/%{file.basename}.out" "%{file.relpath}"'
   }

   -- One or more outputs resulting from the build (required)
   buildoutputs { '%{cfg.objdir}/%{file.basename}.c' }

   -- One or more additional dependencies for this build command (optional)
   buildinputs { 'path/to/file1.ext', 'path/to/file2.ext' }

[Jarod42]

Rules (with propertydefinition) might help:

rule "myrule"
	display "My custom rule"
	fileextension ".lua"

	propertydefinition {
		name = "mycustomflags",
		display = "mycustomflags short desc",
		description = "mycustomflags long desc",
		kind "string"
	}

	-- A message to display while this build step is running (optional)
	buildmessage 'Compiling %{file.relpath}'

	-- One or more commands to run (required)
	buildcommands {
		'luac %{mycustomflags} -o "%{cfg.objdir}/%{file.basename}.out" "%{file.relpath}"'
	}

	-- One or more outputs resulting from the build (required)
	buildoutputs { '%{cfg.objdir}/%{file.basename}.c' }

	-- One or more additional dependencies for this build command (optional)
	buildinputs { 'path/to/file1.ext', 'path/to/file2.ext' }

project "app"
  rules { "myrule" }
  filter {"configurations:not Dev-*", "system:windows"}
    mycustomflags "-bla -O -G" -- Not sure space is supported BTW, using list might be better. '/' might have issue too.

  filter {"configurations:Rel-*", "system:windows"}
    mycustomflags {"-O"}

  filter {} -- reset filter

Else there is premake.api.register, but not sure it should be exposed to users.

premake.api.register {
  name = "mycustomflags",
  scope = "config",
  kind = "string"
}

buildcommands {
	'luac %{cfg.mycustomflags} -o "%{cfg.objdir}/%{file.basename}.out" "%{file.relpath}"'
}

[fhoenig]

This is Visual Studio only, correct?

[Jarod42]

From my tests, only xcode4 and gmake (but not gmake2) don't support custom rules.

[fhoenig]

makes sense. Thank you.