llvm-project/libcxx/test/lit.cfg.py

# All the Lit configuration is handled in the site configs -- this file is only
# left as a canary to catch invocations of Lit that do not go through llvm-lit.
#
# Invocations that go through llvm-lit will automatically use the right Lit
# site configuration inside the build directory.

lit_config.fatal(
    "You seem to be running Lit directly -- you should be running Lit through "
    "<build>/bin/llvm-lit, which will ensure that the right Lit configuration "
    "file is used.")
[libc++] Allow specifying custom Lit config files Before this patch, the libc++ test suite first loads lit.site.cfg (generated by CMake), and then lit.cfg. It's also possible to load lit.cfg before lit.site.cfg and to point to a custom lit.site.cfg file using '--param=libcxx_site_config'. However, in that case, lit.cfg still relies on the site configuration filling up the 'config' object like the default lit.site.cfg file does, which isn't flexible enough. This commit simplifies the setup by having just a single Lit site config file per CMake configuration, and always loading exactly that config file. However, the config file to use can be selected when setting up CMake via the LIBCXX_TEST_CONFIG setting. Furthermore, the site configs are entirely standalone, which means that a new site config can be added that doesn't need to conform what's expected by config.py. Differential Revision: https://reviews.llvm.org/D81846 2020-06-12 15:19:55 -04:00			`# All the Lit configuration is handled in the site configs -- this file is only`
			`# left as a canary to catch invocations of Lit that do not go through llvm-lit.`
			`#`
			`# Invocations that go through llvm-lit will automatically use the right Lit`
			`# site configuration inside the build directory.`

			`lit_config.fatal(`
			`"You seem to be running Lit directly -- you should be running Lit through "`
			`"<build>/bin/llvm-lit, which will ensure that the right Lit configuration "`
			`"file is used.")`