Mercurial > hg > sonic-visualiser

comparison INSTALL.txt @ 2594:2de306979a2a sv_v4.2

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Minor updates to debug and other wording for 4.2; fix failure to show plugin population warning dialog
author Chris Cannam
date Fri, 14 Aug 2020 10:48:29 +0100
parents 27de601a2729
children
comparison
equal deleted inserted replaced
2593:bc882961a233 2594:2de306979a2a
1 1
2 How to compile Sonic Visualiser from source 2 How to compile Sonic Visualiser from source
3 =========================================== 3 ===========================================
4 4
5 (NOTE: Refer also to .travis.yml and .appveyor.yml to see what the 5 (NOTE: Refer also to .travis.yml and .appveyor.yml to how the
6 continuous-integration processes do to run a build) 6 continuous-integration processes run a build)
7 7
8 On Windows and Mac is it actually easier to build from a checkout of 8 On Windows and Mac it is perhaps easier to build from a checkout of
9 the Mercurial repository (be sure to update to the appropriate tag if 9 the Mercurial repository (be sure to update to the appropriate tag if
10 you need a specific release) than it is to build from an official 10 you need a specific release) than it is to build from an official
11 Sonic Visualiser source release package. This is because the 11 Sonic Visualiser source release package. This is because the
12 repository checkout pulls in some required library builds, while the 12 repository checkout pulls in some required library builds, while the
13 source package contains only Sonic Visualiser code. 13 source package contains only Sonic Visualiser code.
14
15 On Linux it is simpler to build from a source package.
14 16
15 17
16 Windows 18 Windows
17 ------- 19 -------
18 20
88 For Cap'n Proto you will need v0.6 or newer. 90 For Cap'n Proto you will need v0.6 or newer.
89 91
90 For the rest, if you happen to be using a Debian-based Linux, you 92 For the rest, if you happen to be using a Debian-based Linux, you
91 probably want to apt install something like the following packages: 93 probably want to apt install something like the following packages:
92 94
93 build-essential libbz2-dev libfftw3-dev libfishsound1-dev 95 build-essential libbz2-dev libfftw3-dev libfishsound1-dev libid3tag0-dev liblo-dev liblrdf0-dev libmad0-dev liboggz2-dev libopus-dev libopusfile-dev libpulse-dev libsamplerate-dev libsndfile-dev libsord-dev libxml2-utils portaudio19-dev qt5-default libqt5svg5-dev raptor2-utils librubberband-dev capnproto libcapnp-dev git mercurial autoconf automake libtool mlton
94 libid3tag0-dev liblo-dev liblrdf0-dev libmad0-dev liboggz2-dev
95 libopus-dev libopusfile-dev libpulse-dev libsamplerate-dev
96 libsndfile-dev libsord-dev libxml2-utils portaudio19-dev qt5-default
97 libqt5svg5-dev raptor2-utils librubberband-dev libcapnp-dev git mercurial
98 autoconf automake libtool mlton
99 96
100 If you are building Sonic Visualiser from a repository checkout, then 97 If you are building Sonic Visualiser from a repository checkout, then
101 the configure script will use Repoint to obtain further checkouts of 98 the configure script will use Repoint to obtain further checkouts of
102 various modules. You will need to have a SML compiler installed for 99 various dependencies. You will need to have a SML compiler installed
103 this to work, such as SML/NJ, MLton, or Poly/ML - hence the presence 100 for this to work, such as SML/NJ, MLton, or Poly/ML - hence the
104 of mlton in the Debian package list above. This is not necessary when 101 presence of mlton in the Debian package list above. This is not
105 building from an official Sonic Visualiser source release. 102 necessary when building from an official Sonic Visualiser source
103 release.
106 104