Premake alternative to the CMake interface library

Is there a Premake alternative to the CMake concept of an 'interface' library?

An 'interface' library has the following properties when linking against it:

• It adds whatever libraries are defined inside this 'interface' library (not the main advantage)
• It adds whatever preprocessor macro's / conditions are set
• It adds include paths
• It adds link paths
• .. probably more?

The main advantage I see with this is that we don't have to pollute the preprocessor macro's / include / link paths for all projects, just for the projects that need it.

Given this pseudo premake5.lua file:

project "gsl"
    kind "Interface"
    includedirs { "gsl/include" }
    defines { "HAS_GSL" }

project "example_1"
    kind "ConsoleApp"
    files { "main.cpp" }
    links { "gsl" }

project "example_2"
    kind "ConsoleApp"
    files { "main.cpp" }

This would mean that example_1 has the folder gsl/include added to the include paths, and the define HAS_GSL set.

The issue names no repository files, tests, or entry points. Start by reviewing Premake's project and link handling against the described CMake interface-library behavior. Done means determining whether the requested target-scoped propagation of libraries, defines, include paths, and link paths is supported or defining the feature needed to provide it.