meson/test cases/unit/100 custom target name/meson.build

project('custom target name', 'c')

python = find_program('python3')

# Name argument is optional and should default to 'file.txt'
custom_target(
  input: 'file.txt.in',
  output: '@BASENAME@',
  command: [python, '--version'],
  build_by_default: true,
  capture: true,
)

subdir('subdir')
Make custom_target() name argument optional 3 years ago			`project('custom target name', 'c')`

test cases: use best practices method to find the python3 program We do not need the python module's find_installation() for this, as this does various things to set up building and installing python modules (pure python and C-API). This functionality is already tested in the python tests. Elsewhere, when we just need an interpreter capable of running python scripts in order to guarantee a useful scripting language for custom commands, it suffices to use find_program(), which does not run an introspection script or do module imports, and is thus faster and a bit cleaner. Either way, both methods are guaranteed to find the python3 interpreter, deferring to mesonlib.python_command for that guarantee. test "71 summary" can sometimes return the python command with the ".exe" part all uppercased for mysterious Windows reasons. Smooth this over with ExternalProgram. 3 years ago			`python = find_program('python3')`
Make custom_target() name argument optional 3 years ago
			`# Name argument is optional and should default to 'file.txt'`
			`custom_target(`
			`input: 'file.txt.in',`
			`output: '@BASENAME@',`
			`command: [python, '--version'],`
			`build_by_default: true,`
			`capture: true,`
			`)`

			`subdir('subdir')`