Sam Edwards d008037244 CMake: Use Python::Module, not Python::Python, for extension linkage ... CMake 3.15+ provides the former, which extension modules should link against in order to ensure the ABI-appropriate linkage for the platform. For older versions of CMake, try to hack up the correct linkage for the platform. If the platform isn't recognized, tell the user to upgrade CMake. This also tweaks p3pystub just a bit, since now it's actually relied upon to resolve runtime link issues when p3dcparse pulls in direct, as p3dcparse doesn't link against Python at all.		2019-08-15 16:47:53 -06:00
..
cppparser	CMake: Neatly format everything for readability and consistency	2019-04-14 22:37:18 -06:00
dconfig	CMake: Assign COMPONENT and EXPORT to all targets	2018-12-06 17:48:44 -07:00
dtoolbase	CMake: Suppress $(EFFECTIVE_PLATFORM_NAME).	2019-06-27 17:38:18 -06:00
dtoolutil	CMake: Separate composite files by extension.	2019-06-27 17:38:18 -06:00
interrogate	CMake: Use Python::Module, not Python::Python, for extension linkage	2019-08-15 16:47:53 -06:00
interrogatedb	CMake: Neatly format everything for readability and consistency	2019-04-14 22:37:18 -06:00
parser-inc	Give istream/ostream a friendlier file-like interface for Python	2019-05-12 15:46:14 +02:00
prc	CMake: Don't compile PRC's encryptStream unless we have OpenSSL.	2019-06-27 17:38:18 -06:00
prckeys	general: Distinguish local/system includes	2018-11-10 18:00:10 -07:00
pystub	CMake: Use Python::Module, not Python::Python, for extension linkage	2019-08-15 16:47:53 -06:00
test_interrogate	Remove pystub dependency from interrogate and friends	2018-11-06 21:49:17 +01:00