move Linux build instructions to code repo from wiki#3657
move Linux build instructions to code repo from wiki#3657Be-ing wants to merge 2 commits intomixxxdj:2.3from
Conversation
Co-authored-by: Jan Holthuis <holthuis.jan@googlemail.com>
Holzhaus
left a comment
Holzhaus
left a comment
There was a problem hiding this comment.
IMHO there should be a single install file.
The only thing that really differs is how to install dependencies and we could just explain what the dependencies are and then put a link to the wiki or refer to a section in the "appendix" of the file for more detailed info how to install dependencies on macOS/Windows/$Distro.
| ``` sh | ||
| sudo dnf groupinstall "Development Tools" | ||
| sudo dnf install gcc-c++ ccache qt5-declarative-devel fdk-aac-free | ||
| sudo dnf builddep mixxx | ||
| ``` |
There was a problem hiding this comment.
This would be easier to read on the terminal if we indent by 4 spaces instead of using fenced code blocks.
| ## Non-System Qt | ||
|
|
||
| To build Mixxx with a version of Qt older or newer than your distribution's package manager, download the latest [Qt source | ||
| code](https://download.qt.io/archive/qt/). For each Qt version, it is available at that link in a directory called "single" and has a filename like `qt-everywhere-src-VERSION.tar.xz`. Extract that archive and compile the source code: | ||
|
|
||
| ```shell | ||
| tar xf qt-everywhere-src-VERSION.tar.xz | ||
| cd qt-everywhere-src-VERSION | ||
| ./configure -prefix /path/to/qt/install -system-sqlite -sql-sqlite -qt-zlib -opensource -confirm-license -nomake examples -nomake tests -skip qt3d -skip qtwebengine | ||
| make -j`nproc` | ||
| make install | ||
| ``` | ||
|
|
||
| Append `-DCMAKE_PREFIX_PATH=/path/to/qt/install` (where `/path/to/qt/install` is the path you used when building Qt) to the cmake configure command to instruct cmake to prefer the Qt version from that path. |
There was a problem hiding this comment.
This should be removed. We can just put a link to Qt's build instructions if it's really deemed necessary to mention this explicitly. But IMHO the better approach is to just explain what CMAKE_PREFIX_PATH can be used to add additional search directories for dependencies.
There was a problem hiding this comment.
"... for example to build with non-system Qt (link to our wiki in case our instructions are easier to digest than having to collect it from various stackoverflow answers)
|
This PR is marked as stale because it has been open 90 days with no activity. |
github-actions
bot
added
the
stale
|
Closing in favor of #4432 which adds a BUILDING.md file documenting the build processes for all supported OSes. |
3 participants
The Arch Linux instructions are rather verbose but I don't use Arch so I don't know how to improve them.