Dylan Baker 23d3b98fc1 split mesonlib into a package ... Currently mesonlib does some import tricks to figure out whether it needs to use windows or posix specific functions. This is a little hacky, but works fine. However, the way the typing stubs are implemented for the msvcrt and fnctl modules will cause mypy to fail on the other platform, since the functions are not implemented. To aleviate this (and for slightly cleaner design), I've split mesonlib into a pacakge with three modules. A universal module contains all of the platform agnositc code, a win32 module contains window specific code, a posix module contains the posix specific code, and a platform module contains no-op implementations. Then the package's __init__ file imports all of the universal functions and all of the functions from the approriate platform module, or the no-op versions as fallbacks. This makes mypy happy, and avoids `if`ing all over the code to switch between the platform specific code.		2021-01-23 12:48:29 +01:00
..
data	Fix misspells	2021-01-13 12:53:10 -05:00
__init__.py	cmake: ignore CMAKE_TOOLCHAIN_FILE and CMAKE_PROJECT_INCLUDE to avoid conflicts with the meson CMake logic	2020-10-16 20:44:04 +02:00
client.py	use real pathlib module	2020-11-20 15:08:40 -08:00
common.py	use real pathlib module	2020-11-20 15:08:40 -08:00
executor.py	move CMAKE_PREFIX_PATH env var handling to environment	2021-01-11 11:15:06 -08:00
fileapi.py	use real pathlib module	2020-11-20 15:08:40 -08:00
generator.py	typing: fully annotate cmake.generator	2020-09-28 13:51:19 +02:00
interpreter.py	split mesonlib into a package	2021-01-23 12:48:29 +01:00
toolchain.py	use real pathlib module	2020-11-20 15:08:40 -08:00
traceparser.py	Fix misspells	2021-01-13 12:53:10 -05:00