On 07/27/2018 12:34 PM, John Paul Adrian Glaubitz wrote:
>> I don't know if it's possible at all to build everything but qdoc. And the
>> effect of this could be many packages starting to FTBFS.
>
> Unlikely. I don't know any project that has a hard dependency on
> documentation.
This part of debian/rules is already written such qdoc is not build for
cross-builds,
so why shouldn't it be possible to disable it for some architectures either?
override_dh_auto_clean:
dh_auto_clean
rm -fv .qmake.cache
rm -fv debian/qttools5-dev-tools.install
build-doc-tools:
# Build qdoc, qhelpgenerator and qtattributionsscanner tools
cd src; qmake CONFIG+=disable_external_rpath
dh_auto_build -- -Csrc sub-qdoc sub-qtattributionsscanner
cd src/assistant; qmake
dh_auto_build -- -Csrc/assistant sub-qhelpgenerator
override_dh_auto_build-indep: build-doc-tools
cd src/qdoc; qmake
cd src/assistant/help; qmake
dh_auto_build -- docs
ifeq ($(DEB_HOST_ARCH),$(DEB_BUILD_ARCH))
override_dh_auto_build-arch: build-doc-tools
# Rebuild the internal assistant.qch which is used as a resource
cd src/assistant/assistant/doc/internal; qmake
dh_auto_build -- -Csrc/assistant/assistant/doc/internal docs
mv doc/assistant.qch src/assistant/assistant/assistant.qch
dh_auto_build
endif
The actual documentation is only generated in override_dh_auto_build-indep
using the build tools generated in build-doc-tools. But if we're not
building any documentation in a binary-arch build, why should we build
the documentation tools either?
For openjdk-X, the documentation is generated using pandoc which isn't
available on every architecture either, yet the binary-arch target of
openjdk-X builds on every architecture.
So, I'm convinced the problem can be solved with better packaging.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
