aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCody Northrop <cody@lunarg.com>2015-10-21 13:32:58 -0400
committerCody Northrop <cody@lunarg.com>2015-10-21 13:32:58 -0400
commit6b6c6aa477339cc6ff8c9fc6906c03de80ddec40 (patch)
treee085a2e0d9f46f822dff773178c05582505c29ea
parent04436505fd6bcf9dc8c1c7663a7b28b2f23dd05b (diff)
downloadusermoji-6b6c6aa477339cc6ff8c9fc6906c03de80ddec40.tar.xz
Fix "_out64" -> "build" references accidentally removed
-rw-r--r--BUILD.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/BUILD.md b/BUILD.md
index d52e43ce..e753714d 100644
--- a/BUILD.md
+++ b/BUILD.md
@@ -233,12 +233,12 @@ Example debug build (e.g. in a "Developer Command Prompt for VS2013" window):
```
cd LoaderAndTools # cd to the root of the Vulkan git repository
update_external_sources.bat --build-glslang
-mkdir _out64
-cd _out64
+mkdir build
+cd build
cmake -G "Visual Studio 12 Win64" ..
```
-At this point, you can use Windows Explorer to launch Visual Studio by double-clicking on the "VULKAN.sln" file in the \_out64 folder. Once Visual Studio comes up, you can select "Debug" or "Release" from a drop-down list. You can start a build with either the menu (Build->Build Solution), or a keyboard shortcut (Ctrl+Shift+B). As part of the build process, Python scripts will create additional Visual Studio files and projects, along with additional source files. All of these auto-generated files are under the "_out64" folder.
+At this point, you can use Windows Explorer to launch Visual Studio by double-clicking on the "VULKAN.sln" file in the \build folder. Once Visual Studio comes up, you can select "Debug" or "Release" from a drop-down list. You can start a build with either the menu (Build->Build Solution), or a keyboard shortcut (Ctrl+Shift+B). As part of the build process, Python scripts will create additional Visual Studio files and projects, along with additional source files. All of these auto-generated files are under the "build" folder.
VK programs must be able to find and use the VK.dll libary. Make sure it is either installed in the C:\Windows\System32 folder, or the PATH enviroment variable includes the folder that it is located in.