simon-git: halibut (main): Simon Tatham

[Commits to Tartarus hosted VCS]

TL;DR:
  83da455 Allow building the docs even in a cross-compile.

Repository:     https://git.tartarus.org/simon/halibut.git
On the web:     https://git.tartarus.org/?p=simon/halibut.git
Branch updated: main
Committer:      Simon Tatham <anakin at pobox.com>
Date:           2021-10-31 17:37:54

commit 83da455cb2d47382d83f9705747b0027a06dd117
web diff https://git.tartarus.org/?p=simon/halibut.git;a=commitdiff;h=83da455cb2d47382d83f9705747b0027a06dd117;hp=235e6d92f08aba2c8aa354fa4f88abb55d39f82c
Author: Simon Tatham <anakin at pobox.com>
Date:   Sun Oct 31 07:51:02 2021 +0000

    Allow building the docs even in a cross-compile.
    
    Colin Watson points out that in the context of a Debian package build,
    cross-compiling doesn't just need to generate some binaries: your
    cross-build wants to go all the way to 'make install' so that it can
    set up the entire file structure for the cross-built package. So, if
    the cross-build refuses to build the docs, then the docs don't get
    installed, and the Debian machinery has to do some nasty bodging.
    
    Previously this worked OK because the docs Makefile was separate and
    took a HALIBUT parameter to override which binary was used for
    building the docs. So you could just add a parameter to your 'make -C
    doc' to point it at the Halibut binary from the native build you were
    also doing.
    
    Now you can do 'cmake -DNATIVE_HALIBUT=/some/path/to/halibut' in a
    cross-build, and then you get the docs built using _that_ Halibut, so
    the cross-build ends up with a full set of files and can 'make install'.

 doc/CMakeLists.txt | 15 +++++++++++----
 1 file changed, 11 insertions(+), 4 deletions(-)