I've tidied up the code in both of the build scripts used for *nix-like
systems, and the macOS/OSX specific build script helper.
This has been tested on Linux with no issues, but this PR will hopefully
indicate if the changes run without issues on macOS as well.
Signed-off-by: Dom Rodriguez <shymega@shymega.org.uk>
The build_installer.bat file uses Inno Setup to build the installer. It
does currently not check if Inno Setup is installed, and fails with the
message:
The system cannot find the path specified.
Build failed
That message does not explain how to fix the problem. I have added a
loop to search for Inno Setup 6 and 5. The user installed Inno Setup is
preferred over the system installed version. If Inno Setup cannot be
found then it prints an actionable error message.
I have tested it by:
1. Not having Inno Setup installed
2. Running build_installer.bat
3. Checked that the error message appears.
4. Installed Inno Setup 6 for my current user
5. Checked that the error message does not appear.
6. Checked that the installer package is generated
6. Uninstalled Inno Setup 6
7. Installed Inno Setup 6 for all users
8. Checked that the error message does not appear.
9. Checked that the installer package is generated
10. Uninstalled Inno Setup 6
11. Installed Inno Setup 5
12. Checked that the error message does not appear.
13. Checked that the installer package is generated
Azure Pipelines have been made to work well enough for this project. All other CI systems are to be disabled as mentioned dunder #308
Delete the .travis.yml file now that it is not longer needed. It can be recovered from git history if we ever wish to resurrect it.
A separate action will need to be taken by someone with administrator access to the present https://travis-ci.org/debauchee/barrier project to unlink from the system there.
We plan to remove all the CI pipeline apart from Microsoft Azue Pipelines. This was documented under #308 after the Azure Pipeline system was successfully integrated under #303 and shown to provide all the build targetes we needed.
As there are presently have 4 seperate main build targes. As well as giving the overall master branch status in the Readme (which forms part of the main page on github.com) also show the seperate build status. This makes it clear if a single part fails and gives an obvious indicator that this project works for Linux, Mac and Windows.
This commit adds suppotr for generating a 'compile commands' JSON
file. This provides fairly sufficient autocomplete support for most text
editors, such as (Neo)vim and VS Code. It specifies include paths, and
the compiler arguments used to compile each source file.
Signed-off-by: Dom Rodriguez <shymega@shymega.org.uk>