files

Lots of information missing here; check out the old 4.x documentation for more details.

Some work has been done to make proper per-file configurations possible. It is now possible to specify any configuration value on a file or set of files.

#!lua
configuration "**.x"
  -- configuration for .x files

These improvements are available in all of the "next-gen" actions, and just waiting on support for specific configuration values to be written into the exporters.

One caveat: in order to apply configuration values you must use a positive filter match.

#!lua
-- this will work
configuration { "**.lua or **.x or **.png" }

-- this will not; no "not" allowed
configuration { "not **.cpp" }

This rule is to prevent terms like "not Debug" from matching against file names when building file configurations.