1 files changed, 82 insertions, 9 deletions
diff --git a/share/man/man5/port-modules.5 b/share/man/man5/port-modules.5
index ea4376cdb7b..d1dc996b00d 100644
--- a/share/man/man5/port-modules.5
+++ b/share/man/man5/port-modules.5
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: port-modules.5,v 1.201 2016/03/22 16:02:02 naddy Exp $
+.\"	$OpenBSD: port-modules.5,v 1.202 2016/03/26 21:27:01 zhuk Exp $
 .\"
 .\" Copyright (c) 2008 Marc Espie
 .\"
@@ -24,7 +24,7 @@
 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: March 22 2016 $
+.Dd $Mdocdate: March 26 2016 $
 .Dt PORT-MODULES 5
 .Os
 .Sh NAME
@@ -597,6 +597,65 @@ It appends
 .Pa devel/pmk
 to
 .Ev BUILD_DEPENDS .
+.It devel/qmake
+This module allows to automate usage of qmake, independently of actual
+version of Qt being used.
+This module requires that one of the
+.Pa x11/qt4
+or
+.Pa x11/qt5
+to be used as well.
+.Pp
+If
+.Ev CONFIGURE_STYLE
+was not set before, sets its value to
+.Sq qmake .
+If
+.Ev CONFIGURE_STYLE
+contains
+.Sq qmake
+the module will define each of the
+.Ar do-build
+and
+.Ar do-install
+targets, unless port already defines one; also,
+.Ev SEPARATE_BUILD
+will be set to
+.Sq Yes
+unless it's already set to some value.
+.Pp
+The following variables could be used in qmake-based ports:
+.Bl -tag -width 1234
+.It Ev MODQMAKE_ARGS
+Additional arguments for qmake invocation.
+The module already defines some.
+.It Ev MODQMAKE_INSTALL_ROOT
+Root directory for fake install.
+Normally, it's a WRKINST, but some (broken) ports require another value,
+like PREFIX.
+.It Ev MODQMAKE_PROJECTS
+List of qmake project files to be used, relative to WRKSRC.
+Directories containing those projects could be used as well,
+see qmake documentation for details.
+Defaults to
+.Sq \&. ,
+which means the (only) project in WRKSRC directory.
+.It Ev MODQMAKE_build
+Actual commands that module will use to build all
+.Ev MODQMAKE_PROJECTS
+provided.
+To be used in complicated cases, when port have to use its own
+.Ar do-build
+target or mix different
+.Ev CONFIGURE_STYLE
+values.
+.It Ev MODQMAKE_install
+Same as for
+.Ev MODQMAKE_build ,
+but used in
+.Ar do-install
+stage.
+.El
 .It devel/scons
 Adds
 .Pa devel/scons
@@ -1768,14 +1827,16 @@ unless
 .Ev MODKDE4_RESOURCES
 is set to
 .Sq Yes .
-.It x11/qt3 and x11/qt4
-Both qt modules share a common
+.It x11/qt3, x11/qt4 and x11/qt5
+All qt* modules share a common
 .Ev MODQT_*
 namespace for simple ports.
 The qt3 module also defines the same variables under
-.Ev MODQT3_*
-and the qt4 module also defines the same variables under
-.Ev MODQT4_* ,
+.Ev MODQT3_* ,
+the qt4 module also defines the same variables under
+.Ev MODQT4_*
+and the qt5 module also defines the same variables under
+.Ev MODQT5_* ,
 to allow ports to use both modules, such as
 .Pa print/poppler .
 .Pp
@@ -1790,11 +1851,13 @@ as the global qt directory location,
 as standard GNU configure-style parameters to locate the include and libraries.
 .Pp
 The location of qt specific tools
-.Nm moc
+.Nm moc,
+.Nm qmake
 and
 .Nm uic
 is available through
-.Ev MODQT*_MOC
+.Ev MODQT*_MOC ,
+.Ev MODQT*_QMAKE
 and
 .Ev MODQT*_UIC .
 .Ev MODQT*_OVERRIDE_UIC
@@ -1804,6 +1867,13 @@ or not.
 The value of
 .Ev MOC
 is always forced to ${MODQT*_MOC}.
+.Pp
+In most cases the
+.Pa devel/qmake
+module should be used instead of using
+.Ev MODQT*_QMAKE
+directly.
+.Pp
 qt4 includes
 .Xr pkg-config 1
 files under a specific location recorded in
@@ -1824,6 +1894,9 @@ Note that qt4 has split its code over several libraries, so the basic
 .Ev WANTLIB
 only refers to QtCore.
 Other libraries should be added as needed.
+The qt5 module doesn't set
+.Ev MODQT*_WANTLIB
+at all.
 .It x11/tk
 Sets
 .Ev MODTK_VERSION ,