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
@@ -56,12 +57,14 @@ Currently, building from source is the only method to obtain a copy of Lambda.
56
57
* `pre-commit` is used for development git commit hooks and any changes that do not pass the pre-commit checks will not be accepted.
57
58
58
59
#### Rendering API support
59
-
These are the Rendering APIs that are supported on each platform and must be installed manually. More information on how to choose which backend lambda uses on each platform is provided further below.
60
+
These are the Rendering APIs that are supported on each platform and must be
61
+
installed manually. More information on how to choose which backend lambda
62
+
uses on each platform is provided further below.
60
63
* Windows
61
64
* `OpenGL`
62
65
* `Vulkan`
63
66
* `DirectX11`
64
-
* `DirectX12`
67
+
* `DirectX12`
65
68
* Linux
66
69
* `OpenGL`
67
70
* `Vulkan`
@@ -74,7 +77,7 @@ If planning to develop for lambda, you must run the setup script provided by rep
74
77
```bash
75
78
./scripts/setup.sh
76
79
```
77
-
This will initialize pre commit checks for development use and setup git-lfs for asset management.
80
+
This will initialize pre commit checks for development use and setup git-lfs for asset management.
78
81
79
82
In order to validate that lambda successfully compiles, you can build the library by performing a build with cargo.
0 commit comments