diff options
| author | Mark Lobodzinski <mark@lunarg.com> | 2016-06-21 15:51:12 -0600 |
|---|---|---|
| committer | Mark Lobodzinski <mark@lunarg.com> | 2016-06-21 16:31:14 -0600 |
| commit | d3f5fa37594de4936ce4d166898e4214873230e8 (patch) | |
| tree | 5494b1bbbe39761b7b49ab7dcfec87050dbabd38 /layers | |
| parent | 21a0d801b2d9b17a665b92cc811afa143175b85c (diff) | |
| download | usermoji-d3f5fa37594de4936ce4d166898e4214873230e8.tar.xz | |
Revert "layers: Update docs for shared utils DLL"
This reverts commit 94dd6081959103c1c9b0bcfda173d4149d5555b9.
Change-Id: Ie5b437d822c5efe6baf0baf2830591f50bf3ee4d
Diffstat (limited to 'layers')
| -rw-r--r-- | layers/README.md | 8 |
1 files changed, 2 insertions, 6 deletions
diff --git a/layers/README.md b/layers/README.md index f2e93e36..d3eecbf1 100644 --- a/layers/README.md +++ b/layers/README.md @@ -68,17 +68,13 @@ layers/device_limits.cpp (name=`VK_LAYER_LUNARG_device_limits`) - This layer is ## Using Layers 1. Build VK loader using normal steps (cmake and make) -2. Place `libVkLayer_<name>.so` or `VkLayer_<name>.dll` in the same directory as your VK test or app: +2. Place `libVkLayer_<name>.so` in the same directory as your VK test or app: - `cp build/layers/libVkLayer_threading.so build/tests` -or- - `copy build\layers/VkLayer_threading.dll build\tests` + `cp build/layer/libVkLayer_threading.so build/tests` This is required for the Loader to be able to scan and enumerate your library. Alternatively, use the `VK_LAYER_PATH` environment variable to specify where the layer libraries reside. - [Windows Only] The VkLayer_utils.dll will also need to be copied into your app directory or to your - system library directory (typically \Windows\System32). - 3. Create a vk_layer_settings.txt file in the same directory to specify how your layers should behave. Model it after the following example: [*vk_layer_settings.txt*](vk_layer_settings.txt) |