The LunarG Vulkan SDK includes a set of C++ Vulkan sample programs. These samples illustrate specific Vulkan entrypoints and their use in implementing graphical features.
The source code of the sample Vulkan programs is available in the
samples directory of the Vulkan SDK.
Build and Run Samples
Note that you will need CMake and Python 3 to build the samples To build and run the sample programs:
Configure the sample program build system for a release build and build the samples.
A shell script is provided to build the samples and their dependencies. Use the following command to run this script.
Alternatively you can manually build the samples as described next. The Vulkan sample programs have a dependency on certain glslang components. These libraries and header files are included in the Vulkan SDK. Specifically, the Linux samples build will pull the libraries from
$VULKAN_SDK/x64_64/lib/glslangand the headers from
$VULKAN_SDK/source/glslang. Use the following commands to build the glslang components.
$ pushd source/glslang $ cmake -H. -Bbuild $ make -C build $ cp build/SPIRV/libSPIRV.a ../../x86_64/lib/glslang $ cp build/glslang/libglslang.a ../../x86_64/lib/glslang $ cp build/glslang/OSDependent/Unix/libOSDependent.a ../../x86_64/lib/glslang $ cp build/OGLCompilersDLL/libOGLCompiler.a ../../x86_64/lib/glslang $ cp build/hlsl/libHLSL.a ../../x86_64/lib/glslang $ popd
Use the following commands to build the samples.
$ pushd samples $ cmake -H. -Bbuild $ make -C build $ popd
When building the samples on Linux, the Xcb windowing system is used by default.
The environment variable SAMPLES_WSI_SELECTION can be set to build for a different windowing system. The supported options are XCB and WAYLAND.
$ cmake -H. -Bbuild -DSAMPLES_WSI_SELECTION=WAYLAND
This can be done by either modifying the build_samples.sh script or by building manually.
Make sure CMake, python and MSBuild are in your PATH. The MSBuild path is included automatically when opening
Developer Command Prompt for VS201x, or alternatively can be loaded in a command window by executing 'vsvars32.bat' found in
\Program Files (x86)\Microsoft Visual Studio xx.0\Common7\Tools\.
A Windows batch file build_windows_samples.bat is provided to locate the installed build tools and build the samples and their dependencies. Note that this batch file builds only 64-bit versions of the tools and samples.
If desired to build the samples manually, do so by running the following commands:
> mkdir build > cd build > cmake -G "Visual Studio 14 2015 Win64" .. > msbuild ALL_BUILD.vcxproj /p:Platform=x64 /p:Configuration=Debug /verbosity:quiet > msbuild ALL_BUILD.vcxproj /p:Platform=x64 /p:Configuration=Release /verbosity:quiet > cd ..
within the following directories, in order:
Alternatively you may skip the msbuild steps above, and build within the Visual Studio IDE by opening the VULKAN_SAMPLES.sln file generated by the cmake command.
- The Debug versions of the loader and layers were built with VS 2015.
- If you want to run the samples with the debug version of the loader and layers, you should build the samples with VS 2015.
- Note that VS 2013 and VS 2017 are supported. Attempting to use them with the debug loader and layers will fail on loading MSVCR140.dll.
32-bit support is currently available, but should only be considered at an Alpha level of stability. 32-bit applications and layers have only been validated to a minimal extent.
Verify the build artifacts.
$ cd build/src $ ls
cd src\Release ls
Notice the listed set of Vulkan sample programs. The program name identifies the Vulkan entrypoint or graphical feature implemented in the sample.
Generate the list of samples currently available (Linux).
This script displays each sample filename and a short description of the sample.
Run the textured cube sample program.
This program uses the appropriate Vulkan entrypoints to open a window and draw a textured cube.
Note: The focus of some sample programs may be to enumerate individual features of specific Vulkan entrypoints and may not render to the screen at all.
Examine Sample Code
The Vulkan Samples currently include samples that are both self-contained and those that use external utilities. In future releases, all samples will be self-contained, i.e. all code will be located within the sample source file itself.
A typical sample Vulkan program will, using one or more Vulkan API entrypoints, perform the following activities:
- retrieve the list of instance and device layers available on the system and their extensions
- identify specific extensions supported by the application
- initialize the application and Vulkan instances
- enumerate and select GPU device on the system
- identify and set up the presentation window (OS-specific)
- initialize command/depth/uniform buffers, descriptors, shaders, and pipelines
- bind the buffers, pipelines, and descriptors and submit the command buffer
- present the image in the window
- destroy the objects used
To find code for a specific entrypoint, search for that entrypoint name in all or specific samples.
More detailed information on programming with specific Vulkan API entrypoints will be provided in future SDK releases.
Provide input, feedback, or contribute a New Sample
- Issues and pull requests can be submitted through the Samples source code repository at https://github.com/LunarG/VulkanSamples