From 6f2449f510dc852ca3dfdaf1f5cb9f2fe0f6af8c Mon Sep 17 00:00:00 2001 From: Bill Somerville Date: Wed, 28 Oct 2020 23:32:49 +0000 Subject: [PATCH] Doc updates --- doc/building on MS Windows.txt | 35 +++++++++++++++++++++++++++------- 1 file changed, 28 insertions(+), 7 deletions(-) diff --git a/doc/building on MS Windows.txt b/doc/building on MS Windows.txt index 043e4aac6..8bae6a658 100644 --- a/doc/building on MS Windows.txt +++ b/doc/building on MS Windows.txt @@ -30,12 +30,13 @@ should download the official Qt on-line installer, this allows you to install one or more variants of the Qt SDK and also to maintain and update the installation at a later date. There are many versions and components within versions available, you only need the base 64-bit -MinGW framework for Qt v5.15.0, other components can unchecked within -the on-line installer. The default install location is C:\Qt which is -fine, do not attempt to move the location of the installed libraries -if you decide you want it elsewhere, the installer patches the -libraries for the installed location and it is easier to un-install -and re-install if you wish to change the installed location. +MinGW framework for Qt v5.15.0 and the matching MinGW 8.1.0 64-bit +developer tools, other components can be unchecked within the on-line +installer. The default install location is C:\Qt which is fine, do +not attempt to move the location of the installed libraries if you +decide you want it elsewhere, the installer patches the libraries for +the installed location and it is easier to un-install and re-install +if you wish to change the installed location. CMake ----- @@ -70,4 +71,24 @@ MSYS2 ----- This utility is available from https://www.msys2.org/. Follow the -download and installation instructions there. +download, installation, and initial upgrading instructions there. Once +installed and updated you will need to install some packages, these +are needed to provide the necessary *nix tools and utilities to build +Hamlib from sources. + +Hamlib +------ + +Currently we statically link Hamlib to avoid clashes with +pre-installed DLLs that may be older versions than we support. Once +Hamlib v1.4 is officially released and commonly available we will move +to dynamic linking. Until then Hamlib must be built from +sources. There is a fork of the official Hamlib project which we keep +up to date with the official project master branch, we recommend +building from the 'integration' branch of that fork. The fork is a git +repository which can be cloned with this command: + +git clone git://git.code.sf.net/u/bsomervi/hamlib hamlib +cd hamlib +git checkout integration +