systemd/man/html.in

#!/bin/sh
set -e

if [ -z "$1" ]; then
    echo "Use: $0 page-name (with no section suffix)"
    exit 1
fi

# make sure the rules have been regenrated (in case man/update-man-rules was just run)
ninja -C "@BUILD_ROOT@" version.h

target="man/$1.html"
ninja -C "@BUILD_ROOT@" "$target"
set -x
exec xdg-open "@BUILD_ROOT@/$target"
meson: add build/man/man and build/man/html to build and display pages Man page generation is generally very slow. I prefer to use -Dman=false when developing systemd, and only build specific pages when introducing changes. Those two little helper tools make it easy: $ build/man/man systemd.link $ build/man/html systemd.link will show systemd.link.8 and systemd.link.html from the build directory build/. 2019-05-09 13:23:50 +02:00			`#!/bin/sh`
			`set -e`

			`if [ -z "$1" ]; then`
			`echo "Use: $0 page-name (with no section suffix)"`
			`exit 1`
			`fi`

meson: run a no-op build to generate man rules When a new page is added using man/update-man-rules, ninja doesn't know about the new target until a build is initiated, so build/man/man and build/man/html would fail. Force a trivial build to regenerate the rules before calling 'ninja -t'. 2020-03-23 20:39:23 +01:00			`# make sure the rules have been regenrated (in case man/update-man-rules was just run)`
			`ninja -C "@BUILD_ROOT@" version.h`

meson: add build/man/man and build/man/html to build and display pages Man page generation is generally very slow. I prefer to use -Dman=false when developing systemd, and only build specific pages when introducing changes. Those two little helper tools make it easy: $ build/man/man systemd.link $ build/man/html systemd.link will show systemd.link.8 and systemd.link.html from the build directory build/. 2019-05-09 13:23:50 +02:00			`target="man/$1.html"`
			`ninja -C "@BUILD_ROOT@" "$target"`
			`set -x`
man/man: refer to the right build directory in the helpers I have no idea how this one slipped through. 2019-06-04 17:33:59 +02:00			`exec xdg-open "@BUILD_ROOT@/$target"`