From 8b2d97d7410fe40576ac5847e62038cff005c37a Mon Sep 17 00:00:00 2001
From: assiduous <assiduous@diligentgraphics.com>
Date: Wed, 1 Apr 2020 13:01:33 -0700
Subject: Updated Core and readme

---
 DiligentCore | 2 +-
 README.md    | 5 +++++
 2 files changed, 6 insertions(+), 1 deletion(-)

diff --git a/DiligentCore b/DiligentCore
index cf12976..72eef53 160000
--- a/DiligentCore
+++ b/DiligentCore
@@ -1 +1 @@
-Subproject commit cf12976096e7c1cc36827db3c92ac460ce8e8c6d
+Subproject commit 72eef53a0d290568b61dee06d4739b58325f3b74
diff --git a/README.md b/README.md
index a48df02..930ebb6 100644
--- a/README.md
+++ b/README.md
@@ -352,6 +352,11 @@ For every executable target, the following manual steps have to be performed:
 Please refer to [MoltenVK user guide](https://github.com/KhronosGroup/MoltenVK/blob/master/Docs/MoltenVK_Runtime_UserGuide.md#install)
 for more details. 
 
+By default, the engine will link with dynamic version of MoltenVK library located in LunarG SDK. If this is not desired or an application wants
+to use a library from a specific location, it can provide the full path to the library via `MoltenVK_LIBRARY` CMake variable. When
+`MoltenVK_LIBRARY` is defined, `VULKAN_SDK` is ignored.
+
+
 <a name="build_and_run_integration"></a>
 ## Integrating Diligent Engine with Existing Build System
 
-- 
cgit v1.2.3