Mercurial > minori
view INSTALL @ 266:1a6a5d3a94cd
dep/animone: make bsd.cc and x11.cc actually work
apparently I broke these, and even now the x11 code *still* doesn't want
to work correctly (at least on FreeBSD). half of the PID response codes
are just 0 or the PID for the X server itself... wtf?
maybe dwm just doesn't support the XRes extension, or I'm just stupid.
i don't know.
author | Paper <paper@paper.us.eu.org> |
---|---|
date | Thu, 11 Apr 2024 22:05:41 -0400 |
parents | 06d6c351925c |
children | 703fb7d7c917 |
line wrap: on
line source
This is just like any typical autotools-based project. To install, it's as simple as: 0). autoreconf -i This step is only necessary if you're cloning from the repository. Tarballs will have this step done already. 1). ./configure Configures the build, finds Qt and the necessary runtime libraries. NOTE: If you don't have Qt binaries on your PATH (e.g. MacPorts), you can temporarily add it by prepending `PATH=qt_path:$PATH" before configuring. 2). make Builds the package. 3). make install Installs the package. Use a suitable permission escalator like sudo or doas. In some cases, the configure script will fail to find Qt. To solve this, put the path containing qmake into your PATH or configure pkg-config with the correct paths for Qt[5/6]Widgets. On OS X/macOS, you'll probably want an app bundle. To create this, simply call `scripts/osx/deploy_build.sh` from the build directory. NOTE: This script relies on `macdeployqt` being in your PATH for it to work properly.