Mercurial > minori
comparison INSTALL @ 241:06d6c351925c
*: reorganize resources, +docs, build translations with autotools
| author | Paper <paper@paper.us.eu.org> |
|---|---|
| date | Mon, 22 Jan 2024 16:36:19 -0500 |
| parents | |
| children | 703fb7d7c917 |
comparison
equal
deleted
inserted
replaced
| 240:6ffe42286978 | 241:06d6c351925c |
|---|---|
| 1 This is just like any typical autotools-based project. | |
| 2 | |
| 3 To install, it's as simple as: | |
| 4 0). autoreconf -i | |
| 5 This step is only necessary if you're cloning from the repository. | |
| 6 Tarballs will have this step done already. | |
| 7 1). ./configure | |
| 8 Configures the build, finds Qt and the necessary runtime libraries. | |
| 9 | |
| 10 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 before configuring. | |
| 13 2). make | |
| 14 Builds the package. | |
| 15 3). make install | |
| 16 Installs the package. Use a suitable permission escalator like sudo | |
| 17 or doas. | |
| 18 | |
| 19 In some cases, the configure script will fail to find Qt. To solve this, put the | |
| 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. |