Book Image

Vulkan Cookbook

By : Pawel Lapinski
Book Image

Vulkan Cookbook

By: Pawel Lapinski

Overview of this book

Vulkan is the next generation graphics API released by the Khronos group. It is expected to be the successor to OpenGL and OpenGL ES, which it shares some similarities with such as its cross-platform capabilities, programmed pipeline stages, or nomenclature. Vulkan is a low-level API that gives developers much more control over the hardware, but also adds new responsibilities such as explicit memory and resources management. With it, though, Vulkan is expected to be much faster. This book is your guide to understanding Vulkan through a series of recipes. We start off by teaching you how to create instances in Vulkan and choose the device on which operations will be performed. You will then explore more complex topics such as command buffers, resources and memory management, pipelines, GLSL shaders, render passes, and more. Gradually, the book moves on to teach you advanced rendering techniques, how to draw 3D scenes, and how to improve the performance of your applications. By the end of the book, you will be familiar with the latest advanced techniques implemented with the Vulkan API, which can be used on a wide range of platforms.
Table of Contents (13 chapters)

Converting GLSL shaders to SPIR-V assemblies

The Vulkan API requires us to provide shaders in the form of SPIR-V assemblies. It is a binary, intermediate representation, so writing it manually is a very hard and cumbersome task. It is much easier and quicker to write shader programs in a high-level shading language such as GLSL. After that we just need to convert them into a SPIR-V form using the glslangValidator tool.

How to do it...

  1. Download and install the Vulkan SDK (refer to the Downloading Vulkan SDK recipe from Chapter 1, Instance and Devices).
  2. Open the command prompt/terminal and go to the folder which contains shader files that should be converted.
  1. To convert a GLSL shader stored in the <input> file into a SPIR-V assembly stored in the <output...