OSXBuild31 » History » Version 2
Version 1 (Chris Cannam, 2018-07-12 03:18 PM) → Version 2/3 (Chris Cannam, 2018-07-12 03:26 PM)
h1. Building SV v3.1 on macOS
We bundle miscellaneous dependent library binaries into the @sv-dependency-builds@ subrepo, and so do not use @configure@ on macOS. (It may be possible to do so, using Homebrew packages, but it's untested.)
We *do* require Qt5 be installed externally, either through Homebrew or using the Qt installer. We also need an SML compiler for the Repoint dependency manager.
* Install Qt5, either through Homebrew or using the Qt installer
* Install an SML compiler, e.g. with @brew install polyml@
* In the SV repo, run @./repoint install@ to pull in the subrepos
* Run @qmake -r sonic-visualiser.pro@ (you may have to specify the full path for Qt5 @qmake@)
* Run @make@
This builds a @Sonic Visualiser.app@, but at this point it still contains references to the external Qt libraries so it can't usefully be distributed. The script @deploy/osx/deploy.sh@ fixes these and packages up a @.dmg@ file. (It also code-signs it, which will fail if you don't have the signing keys. Even so, the @.app@ directory and pre-packaging volume should be left in a working state.)
We bundle miscellaneous dependent library binaries into the @sv-dependency-builds@ subrepo, and so do not use @configure@ on macOS. (It may be possible to do so, using Homebrew packages, but it's untested.)
We *do* require Qt5 be installed externally, either through Homebrew or using the Qt installer. We also need an SML compiler for the Repoint dependency manager.
* Install Qt5, either through Homebrew or using the Qt installer
* Install an SML compiler, e.g. with @brew install polyml@
* In the SV repo, run @./repoint install@ to pull in the subrepos
* Run @qmake -r sonic-visualiser.pro@ (you may have to specify the full path for Qt5 @qmake@)
* Run @make@
This builds a @Sonic Visualiser.app@, but at this point it still contains references to the external Qt libraries so it can't usefully be distributed. The script @deploy/osx/deploy.sh@ fixes these and packages up a @.dmg@ file. (It also code-signs it, which will fail if you don't have the signing keys. Even so, the @.app@ directory and pre-packaging volume should be left in a working state.)