Mercurial > minori

comparison INSTALL @ 293:703fb7d7c917

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
INSTALL: update instructions
author Paper <paper@paper.us.eu.org>
date Sun, 12 May 2024 18:06:44 -0400
parents 06d6c351925c
children 1faa72660932
comparison
equal deleted inserted replaced
292:ac1451035c85 293:703fb7d7c917
1 This is just like any typical autotools-based project. 1 This is just like any typical autotools-based project.
2 2
3 To install, it's as simple as: 3 To install, it's as simple as:
4 0). autoreconf -i 4 0). autoreconf -i
5 This step is only necessary if you're cloning from the repository. 5 This step is only necessary if you're cloning from the repository.
6 Tarballs will have this step done already. 6 Tarballs will have this step done already. This step requires autoconf,
7 automake, libtool, pkg-config/pkgconf, and libcurl installed already.
7 1). ./configure 8 1). ./configure
8 Configures the build, finds Qt and the necessary runtime libraries. 9 Configures the build, finds Qt and the necessary runtime libraries.
9 10
10 NOTE: If you don't have Qt binaries on your PATH (e.g. MacPorts), 11 NOTE: If you don't have Qt binaries on your PATH (e.g. MacPorts),
11 you can temporarily add it by prepending `PATH=qt_path:$PATH" 12 you can temporarily add it by prepending `PATH=qt_path:$PATH"
14 Builds the package. 15 Builds the package.
15 3). make install 16 3). make install
16 Installs the package. Use a suitable permission escalator like sudo 17 Installs the package. Use a suitable permission escalator like sudo
17 or doas. 18 or doas.
18 19
19 In some cases, the configure script will fail to find Qt. To solve this, put the 20 On Windows, you'll want to use a Unix-like environment such as msys2 or Cygwin.
20 path containing qmake into your PATH or configure pkg-config with the correct
21 paths for Qt[5/6]Widgets.
22
23 On OS X/macOS, you'll probably want an app bundle. To create this, simply call
24 `scripts/osx/deploy_build.sh` from the build directory.
25 NOTE: This script relies on `macdeployqt` being in your PATH for it to work
26 properly.