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
release_dir: Release/driver# dir of driver binaries within env.CMAKE_BUILD_DIR, VS multi-config uses <CONFIG>/ subfolder
18
+
release_dir: Release # dir of driver binaries within env.CMAKE_BUILD_DIR, VS multi-config uses <CONFIG>/ subfolder
19
19
- os: ubuntu-latest
20
20
triplet: x64-linux
21
21
target: all
22
-
release_dir: driver# makefile single config won't have subfolder
22
+
release_dir: ""# makefile single config won't have subfolder
23
23
env:
24
24
# Indicates the CMake build directory where project files and binaries are being produced.
25
25
CMAKE_BUILD_DIR: ${{ github.workspace }}/build
26
26
# Indicates the location of the vcpkg as a Git submodule of the project repository.
27
27
VCPKG_ROOT: ${{ github.workspace }}/vcpkg
28
28
29
29
steps:
30
-
- uses: actions/checkout@v2
30
+
- uses: actions/checkout@v4
31
31
with:
32
32
submodules: true
33
-
33
+
34
34
- uses: lukka/get-cmake@latest
35
-
36
-
- name: Clone vcpkg
37
-
uses: actions/checkout@v2
38
-
with:
39
-
repository: microsoft/vcpkg
40
-
path: ${{ env.VCPKG_ROOT }}
41
-
submodules: true
35
+
36
+
- name: Get submodule commit hashes
37
+
id: submodule_hashes
38
+
run: git submodule foreach --recursive git rev-parse HEAD > submodule_hashes.txt
42
39
43
40
- name: Restore vcpkg and its artifacts
44
-
uses: actions/cache@v2
41
+
uses: actions/cache@v4
45
42
with:
46
43
# The first path is where vcpkg generates artifacts while consuming the vcpkg.json manifest file.
47
44
# The second path is the location of vcpkg (it contains the vcpkg executable and data files).
@@ -52,12 +49,11 @@ jobs:
52
49
!${{ env.VCPKG_ROOT }}/buildtrees
53
50
!${{ env.VCPKG_ROOT }}/packages
54
51
!${{ env.VCPKG_ROOT }}/downloads
55
-
# The key is composed in a way that it gets properly invalidated: this must happen whenever vcpkg's Git commit id changes, or the list of packages changes. In this case a cache miss must happen and a new entry with a new key with be pushed to GitHub the cache service.
52
+
# The key is composed in a way that it gets properly invalidated: this must happen whenever vcpkg/submodule Git commit id changes, or the list of packages changes. In this case a cache miss must happen and a new entry with a new key with be pushed to GitHub the cache service.
56
53
# The key includes: hash of the vcpkg.json file, the hash of the vcpkg Git commit id, and the used vcpkg's triplet. The vcpkg's commit id would suffice, but computing an hash out it does not harm.
57
54
# Note: given a key, the cache content is immutable. If a cache entry has been created improperly, in order the recreate the right content the key must be changed as well, and it must be brand new (i.e. not existing already).
Copy file name to clipboardExpand all lines: README.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,8 +38,16 @@ okay with this and that you are authorized to provide the above licenses.
38
38
39
39
### Building
40
40
41
-
To build the project with VSCode you need to install two things: [vcpkg](https://vcpkg.io/en/getting-started.html) and [VS Build Tools](https://visualstudio.microsoft.com/downloads/).
41
+
Clone the repo with `git clone --recurse-submodules https://github.com/SlimeVR/SlimeVR-OpenVR-Driver` to clone with all libraries and [vcpkg](https://vcpkg.io/en/getting-started.html) registry.
42
+
43
+
To build the project with VSCode on Windows you need to install [VS Build Tools](https://visualstudio.microsoft.com/downloads/).
44
+
45
+
Run the bootstrap script to build vcpkg binary `.\vcpkg\bootstrap-vcpkg.bat` or `./vcpkg/bootstrap-vcpkg.sh`.
42
46
43
47
After installing vcpkg if you're on Windows, you need to run `vcpkg integrate install` command from the vcpkg folder to integrate it for VSCode.
44
48
45
49
For other systems and IDEs instructions are not available as of now, contributions are welcome.
50
+
51
+
### Updating vcpkg packages
52
+
53
+
To update vcpkg packages set the vcpkg registry submodule to a newer commit and rerun the bootstrap script.
0 commit comments