summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorRusty Wagner <rusty.wagner@gmail.com>2025-11-13 17:45:30 -0500
committerRusty Wagner <rusty.wagner@gmail.com>2025-11-25 18:50:42 -0500
commit269a58437f9da2d46e7fd49712a555722436d6fb (patch)
tree19a17c81dce06466e6abc950e860794d62481859 /docs
parent0317c1a5c51e623a00249ecdefa0c5dd582e0eb1 (diff)
Update to Qt 6.10.1
Diffstat (limited to 'docs')
-rw-r--r--docs/about/open-source.md10
-rw-r--r--docs/dev/plugins.md4
2 files changed, 7 insertions, 7 deletions
diff --git a/docs/about/open-source.md b/docs/about/open-source.md
index c3460984..43300b21 100644
--- a/docs/about/open-source.md
+++ b/docs/about/open-source.md
@@ -79,14 +79,14 @@ Due to its different document generation system, all our rust dependencies and t
## Building Qt
-Binary Ninja uses [Qt 6.8] under an LGPLv3 license which requires that we host the original sources used to build Qt for
+Binary Ninja uses [Qt 6.10] under an LGPLv3 license which requires that we host the original sources used to build Qt for
our application along with instructions on how that source may be re-built and can replace the version of Qt shipped
with Binary Ninja.
Please note that we offer no support for running Binary Ninja with modified Qt libraries.
1. Follow the installation requirements on the [Building Qt 6 from Git] page.
-2. Download the Qt 6.8.2 [tarball] from binary.ninja. The Qt code has a [patch] applied but is ABI compatible with the
+2. Download the Qt 6.10.1 [tarball] from binary.ninja. The Qt code has a [patch] applied but is ABI compatible with the
official Qt release.
3. Next, build Qt with the [qt-build] repository. Alternatively, build Qt using the aforementioned instructions.
4. On macOS, you will need to disable the code-signing signature since it would otherwise prevent changes to binaries or shared libraries.
@@ -96,7 +96,7 @@ Please note that we offer no support for running Binary Ninja with modified Qt l
- On Linux, replace the `libQt6Core.so.6`, `libQt6DBus.so.6`, `libQt6Gui.so.6`, `libQt6Network.so.6`, `libQt6Widgets.so.6`, `libQt6XcbQpa.so.6` files wherever Binary Ninja was extracted.
[Building Qt 6 from Git]: https://wiki.qt.io/Building_Qt_6_from_Git
-[Qt 6.8]: https://www.qt.io/licensing/open-source-lgpl-obligations
+[Qt 6.10]: https://www.qt.io/licensing/open-source-lgpl-obligations
[abseil-cpp]: https://github.com/abseil/abseil-cpp
[abseil-cpp license]: https://github.com/abseil/abseil-cpp/blob/master/LICENSE
[BinExport]: https://github.com/google/binexport
@@ -142,8 +142,8 @@ Please note that we offer no support for running Binary Ninja with modified Qt l
[sphinx]: https://www.sphinx-doc.org/en/master/
[sqlite license]: https://www.sqlite.org/copyright.html
[sqlite]: https://www.sqlite.org/index.html
-[tarball]: https://binary.ninja/qt6.8.2.tar.xz
-[patch]: https://binary.ninja/qt6.8.2.patch
+[tarball]: https://binary.ninja/qt6.10.1.tar.xz
+[patch]: https://binary.ninja/qt6.10.1.patch
[qt-build]: https://github.com/Vector35/qt-build
[yasm license]: https://github.com/yasm/yasm/blob/master/BSD.txt
[yasm]: https://github.com/yasm/yasm
diff --git a/docs/dev/plugins.md b/docs/dev/plugins.md
index 7f0b1901..eba497ec 100644
--- a/docs/dev/plugins.md
+++ b/docs/dev/plugins.md
@@ -290,7 +290,7 @@ automatically detect the plugin target and will compile and install correctly. H
setup for building and live debugging your plugin:
1. If you installed Binary Ninja somewhere other than the default, add an environment variable in your CMake Profile pointing at the installation, e.g.: `BN_INSTALL_DIR=/Applications/Binary Ninja.app`
-2. If you are writing a UI plugin, you will need to include the directory containing `qmake` to the `PATH` Environment Variable in your CMake Profile, e.g.: `PATH=/usr/bin:/bin:/usr/sbin:/sbin:/Users/user/Qt/6.8.2/clang_64/bin`
+2. If you are writing a UI plugin, you will need to include the directory containing `qmake` to the `PATH` Environment Variable in your CMake Profile, e.g.: `PATH=/usr/bin:/bin:/usr/sbin:/sbin:/Users/user/Qt/6.10.1/clang_64/bin`
3. In your Run Configuration's Before Launch steps, add an Install step. This will copy the updated version of your plugin before starting, so you don't have to run Install manually.
4. Set the Executable of your Run Configuration to point to the Binary Ninja executable. This allows you to compile your plugin and start Binary Ninja automatically.
i. On macOS, you will need the full path to /Applications/Binary Ninja.app/Contents/MacOS/binaryninja
@@ -320,7 +320,7 @@ You need to set up a task in `.vscode/tasks.json` to build and install your plug
// You will need this if your Binary Ninja installation is not in the default location
"BN_INSTALL_DIR": "C:\\Users\\User\\AppData\\Local\\Vector35\\BinaryNinja",
// You will need this if you are writing a UI plugin
- "PATH": "C:\\Users\\User\\Qt\\6.8.2\\msvc2019_64\\bin"
+ "PATH": "C:\\Users\\User\\Qt\\6.10.1\\msvc2019_64\\bin"
}
}
}