You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: en/02_Development_environment.md
+14-3
Original file line number
Diff line number
Diff line change
@@ -195,8 +195,8 @@ The number of extensions should be non-zero. Congratulations, you're all set for
195
195
196
196
## Linux
197
197
198
-
These instructions will be aimed at Ubuntuand Fedora users, but you may be able to follow
199
-
along by changing the `apt` and `dnf`commands to the package manager commands that are appropriate for you. You should have a compiler that supports C++17 (GCC 7+ or Clang 5+). You'll also need make.
198
+
These instructions will be aimed at Ubuntu, Fedora and Arch Linux users, but you may be able to follow
199
+
along by changing the package manager-specific commands to the ones that are appropriate for you. You should have a compiler that supports C++17 (GCC 7+ or Clang 5+). You'll also need `make`.
200
200
201
201
### Vulkan Packages
202
202
@@ -206,6 +206,9 @@ The most important components you'll need for developing Vulkan applications on
206
206
*`sudo apt install libvulkan-dev` or `sudo dnf install vulkan-loader-devel` : Installs Vulkan loader. The loader looks up the functions in the driver at runtime, similarly to GLEW for OpenGL - if you're familiar with that.
207
207
*`sudo apt install vulkan-validationlayers-dev spirv-tools` or `sudo dnf install mesa-vulkan-devel vulkan-validation-layers-devel`: Installs the standard validation layers and required SPIR-V tools. These are crucial when debugging Vulkan applications, and we'll discuss them in the upcoming chapter.
208
208
209
+
On Arch Linux, you can run `sudo pacman -S vulkan-devel` to install all the
210
+
required tools above.
211
+
209
212
If installation was successful, you should be all set with the Vulkan portion. Remember to run
210
213
`vkcube` and ensure you see the following pop up in a window:
211
214
@@ -236,6 +239,10 @@ or
236
239
```bash
237
240
sudo dnf install glfw-devel
238
241
```
242
+
or
243
+
```bash
244
+
sudo pacman -S glfw-wayland # glfw-x11 for X11 users
245
+
```
239
246
240
247
### GLM
241
248
@@ -254,12 +261,16 @@ or
254
261
```bash
255
262
sudo dnf install glm-devel
256
263
```
264
+
or
265
+
```bash
266
+
sudo pacman -S glm
267
+
```
257
268
258
269
### Shader Compiler
259
270
260
271
We have just about all we need, except we'll want a program to compile shaders from the human-readable [GLSL](https://en.wikipedia.org/wiki/OpenGL_Shading_Language) to bytecode.
261
272
262
-
Two popular shader compilers are Khronos Group's `glslangValidator` and Google's `glslc`. The latter has a familiar GCC- and Clang-like usage, so we'll go with that: on Ubuntu, download Google's [unofficial binaries](https://github.com/google/shaderc/blob/main/downloads.md) and copy `glslc` to your `/usr/local/bin`. Note you may need to `sudo` depending on your permissions. On Fedora use `sudo dnf install glslc`. To test, run `glslc` and it should rightfully complain we didn't pass any shaders to compile:
273
+
Two popular shader compilers are Khronos Group's `glslangValidator` and Google's `glslc`. The latter has a familiar GCC- and Clang-like usage, so we'll go with that: on Ubuntu, download Google's [unofficial binaries](https://github.com/google/shaderc/blob/main/downloads.md) and copy `glslc` to your `/usr/local/bin`. Note you may need to `sudo` depending on your permissions. On Fedora use `sudo dnf install glslc`, while on Arch Linux run `sudo pacman -S shaderc`. To test, run `glslc` and it should rightfully complain we didn't pass any shaders to compile:
0 commit comments