Docs - update paths to reflect removal of app/gui/qt dir

Author: samaaron

BUILD-LINUX.md

@@ -60,15 +60,15 @@ Note: please make sure that you have gcc12 installed. Compiling vcpkg dependenci
 ### 1.1 Debian
 The following is a rough list of Debian packages that are needed that can serve as a starting position:
 ```bash
-sudo apt-get install -y build-essential git libssl-dev ruby-dev elixir erlang-dev erlang-xmerl qt6-tools-dev qt6-tools-dev-tools libqt6svg6-dev libqt6opengl6-dev supercollider-server sc3-plugins-server alsa-utils  libasound2-dev cmake ninja-build pipewire-jack libspa-0.2-jack qt6-wayland libwayland-dev libxkbcommon-dev libegl1-mesa-dev libx11-dev libxft-dev libxext-dev qpwgraph compton
+sudo apt-get install -y build-essential git libssl-dev ruby-dev elixir erlang-dev erlang-xmerl qt6-tools-dev qt6-tools-dev-tools libqt6svg6-dev libqt6opengl6-dev supercollider-server sc3-plugins-server alsa-utils  libasound2-dev cmake ninja-build pipewire-jack libspa-0.2-jack qt6-wayland libwayland-dev libxkbcommon-dev libegl1-mesa-dev libx11-dev libxft-dev libxext-dev qpwgraph compton m4 libaubio-dev libpng-dev libboost-all-dev
 ```
 
 *Notes:*
 
 1. Check the version of `Qt` after package installation.
 
 * Check your current Qt version with `qmake --version`.
-*  If it is too old (see dependency list above) you should find a way to update `Qt` before going to the build step.
+* If it is too old (see dependency list above) you should find a way to update `Qt` before going to the build step.
 
 3. The main repositories may not have a recent enough version of
 Elixir. If this is the case, you can install it via **one** of the

BUILD-MAC.md

@@ -2,7 +2,6 @@
 
 Hello there lovely macOS user - welcome to our build instructions.
 
-
 ### Installing vs Building
 
 These instructions are for people wanting to build/compile their own
@@ -21,21 +20,19 @@ https://in-thread.sonic-pi.net
 OK, so just to get you prepared, we're going to do a few things:
 
 1. Install the various dependencies that Sonic Pi needs both to be built
-and to run
+   and to run
 2. Build Sonic Pi using a command line script
 3. Start your new Sonic Pi using your newly built app
 
-
 ### Notes
 
-* If you have any issues building Sonic Pi on macOS please open up an
+- If you have any issues building Sonic Pi on macOS please open up an
   issue on GitHub and we'll try our best to assist you:
   https://github.com/sonic-pi-net/sonic-pi/issues
-* These build instructions assume you're running under macOS 12+. If
+- These build instructions assume you're running under macOS 12+. If
   you're using an older version of macOS some steps may need
   modification.
 
-
 ## 1. Installing Dependencies
 
 In order to build Sonic Pi's various components, we need to install a
@@ -45,15 +42,13 @@ few dependencies:
 2. Homebrew
 3. All other dependencies - Qt6 (6.2+), CMake (3.18+), Elixir(1.13+), pkg-config
 
-
 ### 1.1 Install Xcode
 
 Firstly open the App Store and install the latest Xcode (12.1 at the
 time of writing). Also install the command line tools which will give
 you access to a compiler necessary to build the GUI and other
 components.
 
-
 ### 1.2 Install Homebrew
 
 Install [Homebrew](https://brew.sh) by running the following within a terminal:
@@ -68,7 +63,6 @@ trusted system used by many developers globally you're always
 recommended to read any scripts before executing them to reassure
 yourself they aren't doing anything malicious._
 
-
 ### 1.3 Install all other dependencies
 
 Once you have Homebrew installed, pulling in the rest of the
@@ -79,7 +73,6 @@ brew install qt cmake elixir pkg-config
 
 ```
 
-
 ## 2. Preparing the Build
 
 Once we have installed all the dependencies, we're almost ready to build
@@ -102,7 +95,6 @@ From now on these instructions will assume you downloaded the source
 into `~/Development/sonic-pi`. If you used a different location be sure to
 change any future references to `~/Development/sonic-pi` to your chosen location.
 
-
 ## 3. Running the Build
 
 Now we're ready to build everything. This is achieved with one single command
@@ -113,7 +105,6 @@ which will:
 2. Run the config script to set up the build system.
 3. Run cmake to build the final entry-point binary.
 
-
 ### 3.1 Move to the app directory
 
 Firstly, we need to change to the `app` directory at the root of the Sonic Pi repository:
@@ -122,7 +113,6 @@ Firstly, we need to change to the `app` directory at the root of the Sonic Pi re
 cd ~/Development/sonic-pi/app
 ```
 
-
 ### 3.2 Build All
 
 Next we run the build-all script for macOS:
@@ -131,25 +121,22 @@ Next we run the build-all script for macOS:
 ./mac-build-all.sh
 ```
 
-
 ## 4. Start Sonic Pi
 
-Finally, you can run your newly compiled `Sonic Pi` app within the new `build`
+Finally, you can run your newly compiled `Sonic Pi` app within the new `build/gui`
 directly either by double clicking it in the Finder or via the terminal:
 
 ```
-./build/Sonic\ Pi.app/Contents/MacOS/Sonic\ Pi
+./build/gui/Sonic\ Pi.app/Contents/MacOS/Sonic\ Pi
 
 ```
 
-
 ## Good Luck!
 
 Good luck and please share your new live coding adventure with us over on:
 
 https://in-thread.sonic-pi.net
 
-
 #### Anaconda users beware!
 
 Anaconda (a popular data science toolkit) installs a lot of extra programs, including one called `macdeployqt` which conflicts with the build process mentioned above.

BUILD-WINDOWS.md

@@ -227,13 +227,13 @@ win-build-all.bat
 Finally, you can run your newly compiled Sonic Pi from the `build` directory:
 
 ```
-gui\qt\Release\sonic-pi.exe
+gui\Release\sonic-pi.exe
 ```
 
 Or from anywhere using the full path:
 
 ```
-C:\dev\sonic-pi\app\build\gui\qt\Release\sonic-pi.exe
+C:\dev\sonic-pi\app\build\gui\Release\sonic-pi.exe
 ```