@@ -21,7 +21,11 @@ load("@aabtop_rules_qt//:rules_qt_deps2.bzl", "rules_qt_deps2")
21
21
rules_qt_deps2()
22
22
```
23
23
24
- to your ` WORKSPACE ` file.
24
+ to your ` WORKSPACE ` file. Note that by default, it will reference pre-built
25
+ Qt binaries stored as a GitHub release for this repository. If you would like
26
+ to build Qt from source, modify the last line above from ` rules_qt_deps2() ` to
27
+ ` rules_qt_deps2("local") ` , and be prepared to wait a couple of hours.
28
+
25
29
26
30
The rules can be accessed by loading:
27
31
@@ -30,3 +34,19 @@ load("@aabtop_rules_qt//:qt_rules.bzl", "qt_cc_library", "qt_cc_binary", "qt_res
30
34
```
31
35
32
36
See the [ //sample/BUILD] ( sample/BUILD ) file for example usage.
37
+
38
+
39
+ ## Rebuilding the binary releases
40
+
41
+ In order to rebuild the binary versions of Qt referenced in the releases,
42
+ run ` ./build.sh out ` on Linux and ` ./build.bat out `
43
+ on Windows. Note that both of those commands require Docker (or Docker Desktop
44
+ for Windows, in Windows mode) to be installed. You will then find the output
45
+ archive in the ` out/ ` folder, which can then be manually uploaded to GitHub as a
46
+ release. Afterwards, the references to ` aabtop_qt_bin_linux ` and
47
+ ` aabtop_qt_bin_windows ` should be updated in
48
+ [ rules_qt_deps1.bzl] ( rules_qt_deps1.bzl ) .
49
+
50
+ Finally, after the change above to update the releases is merged, the
51
+ instructions in this README file above should be updated to point to the
52
+ new commit hash which references the updated release archives.
0 commit comments