From afe4e6b03fafac765110ddc39d9222fd6a36a94e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andreas=20S=C3=BC=C3=9Fenbach?= Date: Tue, 3 Dec 2019 10:15:06 +0100 Subject: [PATCH] Extent readme on samples and tests. (#449) --- README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index fa3310d..eb3e07c 100644 --- a/README.md +++ b/README.md @@ -410,9 +410,11 @@ Creating a full featured ```DispatchLoaderDynamic``` is a two- to three-step pro ``` After the second step above, the dispatcher is fully functional. Adding the third step can potentially result in more efficient code. -### Samples +### Samples and Tests + +When you configure your project using CMake, you can enable SAMPLES_BUILD to add some sample projects to your solution. Most of them are ports from the LunarG samples, but there are some more, like CreateDebugUtilsMessenger, InstanceVersion, PhysicalDeviceDisplayProperties, PhysicalDeviceExtensions, PhysicalDeviceFeatures, PhysicalDeviceGroups, PhysicalDeviceMemoryProperties, PhysicalDeviceProperties, PhysicalDeviceQueueFamilyProperties, and RayTracing. All those samples should just compile and run. +When you configure your project using CMake, you can enable TESTS_BUILD to add some test projects to your solution. Those tests are just compilation tests and are not required to run. -When you configure your project using CMake, you can enable SAMPLES_BUILD, getting you a port of most of the LunarG samples and one sample named RayTracing featuring the VK_NV_ray_tracing extension. ## See Also