We recommend this if you are working on Mixxx code, but not if you are performing with Mixxx. This ensures that messages about violated debug assertions are not missed between various other debug log messages. If you want to make a debug build, add -DCMAKE_BUILD_TYPE=Debug -DDEBUG_ASSERTIONS_FATAL=ON to the end of the cmake configure command.ĭebug builds should be started with the command line option -debugAssertBreak to trigger a breakpoint in the debugger if debugĪssertions are violated or to abort Mixxx immediately. If you have it elsewhere, use that path instead in the following commands.Ĭcache -set-config=max_size=20.0G Development tips Debug build and assertions These examples assume you have the Mixxx source code at ~/mixxx. Don't use the prefix /usr, because it is reserved for packaged version of Mixxx (deb/rpm/.) and will interfere with the update process of your package manager. usr/local is used as the installation path in this example, but you can set this to anywhere as long as your $PATH environment variable includes a bin directory under the installation path ( /usr/local/bin if the installation path is /usr/local). This step checks if you have all the dependencies installed, similar to the configure script of GNU autotools. This only needs to be done once you don't need to repeat it when you compile Mixxx again. Building and installing Mixxx follows the standard CMake procedures.īefore compiling, you need to configure with CMake. If you're building Mixxx 2.2 or earlier, refer to the old instructions below. configure -prefix /path/to/qt/install -system-sqlite -sql-sqlite -qt-zlib -opensource -confirm-license -nomake examples -nomake tests -skip qt3d -skip qtwebengine
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |