From b9d65606f71799cce5974e0c8fc1c54f159996d7 Mon Sep 17 00:00:00 2001 From: Martin Date: Fri, 15 Mar 2024 22:23:24 +0100 Subject: [PATCH] README update, add solution Crostini graphics issue; build info update Signed-off-by: Martin --- CHANGELOG | 1 + README.md | 3 +++ docs/build.md | 6 ++++-- 3 files changed, 8 insertions(+), 2 deletions(-) diff --git a/CHANGELOG b/CHANGELOG index aadaee28..17dc826b 100644 --- a/CHANGELOG +++ b/CHANGELOG @@ -1,3 +1,4 @@ +2024-03-12 (29dbcca): README update 2024-03-05 (9c1e9e8): fix #399 - update macos build instructions, hack nedded no more 2024-02-24 (3ac5c3a): fw refactoring - no functional change 2024-02-23 (ad43d3b): Merge branch 'wakass-main' - Instrustar 205X support #394 diff --git a/README.md b/README.md index 228676ca..a4eee9fe 100644 --- a/README.md +++ b/README.md @@ -186,6 +186,9 @@ Especially on Windows, this option may be necessary to use the program. It has been reported that the MINGW binary build on some Windows systems had problems with the graphical display and led to a black screen without traces. In these cases, the switch to the MSVC binary build can help. +Similar [issues](https://github.com/OpenHantek/OpenHantek6022/issues/350) with Linux on ChromeOS (Crostini) can be solved by setting the environment variable `LIBGL_ALWAYS_SOFTWARE=1` when using OpenHantek. +This could also be a solution for the above MINGW issue, see e.g. #360 and #388 - not yet confirmed. + The Raspberry Pi build uses OpenGL ES automatically, check also the [graphics driver setup](docs/build.md#raspberrypi). ### USB Access diff --git a/docs/build.md b/docs/build.md index 70ab38f2..974a91e8 100644 --- a/docs/build.md +++ b/docs/build.md @@ -175,6 +175,7 @@ about building on macOS 11.6.8 + Xcode 12.4 (12D4e). As I do not use macOS for development the building is done externally by [GitHub Actions](https://github.com/OpenHantek/OpenHantek6022/actions) who provides [these macOS 11 environments](https://github.com/actions/runner-images/blob/main/images/macos/macos-11-Readme.md). Please check also the file [build_check.yml](https://github.com/OpenHantek/OpenHantek6022/blob/main/.github/workflows/build_check.yml) for info about the building process. + ---- ### [Windows](#windows) @@ -186,6 +187,7 @@ will be closed as invalid! * Compile the software Hints for Visual Studio 2015/2017/2019 users: + * Install the right Qt package that matches your Visual Studio installation. * Build for 64bit. 32bit builds theoretically work, but you are on your own then. * Use the **CMake GUI** to setup all required Qt include and library paths. @@ -194,8 +196,8 @@ Hints for Visual Studio 2015/2017/2019 users: As I do not use Windows for development the building is done externally by [GitHub Actions](https://github.com/OpenHantek/OpenHantek6022/actions) who provides [these Windows environments](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md). -Please check also the file [build_check.yml](https://github.com/OpenHantek/OpenHantek6022/blob/main/.github/workflows/build_check.yml) for info about the building process. -Starting with the update to Visual Studio 2019 for the upcoming OpenHantek6022 version 3.2 only 64bit builds are provided. +Please check also the file [build_check.yml](https://github.com/OpenHantek/OpenHantek6022/blob/main/.github/workflows/build_check.yml) for info about the building process with either MINGW or MSVC. +Starting with the update to Visual Studio 2019 only 64bit builds are provided. #### Signed WinUSB driver for Hantek 6022BE/BL