sphinxcontrib-theme-web2/configure.ac
Rodney, Tiara 39fd5a7bf2
feat(build): init vendor integration
Now, the HTML theme build is daisy-chained to the build of the Sphinx theme,
including a skeleton for watching, which will be part of user-acceptance
testing, which will be sphinx-autobuild building `docs/`.
2025-03-23 19:34:36 +01:00

33 lines
1.1 KiB
Text

AC_INIT
# required in Makefile to ensure proper path resolution during preprocessing
AC_CHECK_PROGS([MAKE], [make])
AC_CHECK_PROGS([REALPATH], [realpath])
AC_CHECK_PROGS([GIT], [git])
AC_CHECK_PROGS([PYTHON3], [python3])
# HTML theme reference dependency for dynamic building, alternatively this could
# be removed and instead the HTML theme reference could be statically integrated
# by storing the build package archive under vendor/ instead and untar the
# archive into src/<whatever>.
AC_MSG_NOTICE([checking for vendor build dependencies...])
AC_CHECK_PROGS([NPM], [npm])
AC_CHECK_PROGS([NODE], [node])
AC_MSG_NOTICE([initializing Git submodules...])
git submodule update --init --remote --recursive
AC_MSG_NOTICE([initializing vendors...])
sh -xc "cd vendor/html-theme-ref && npm install"
AC_MSG_NOTICE([initializing python3 venv...])
python3 -m venv .venv
AC_MSG_NOTICE([installing dependencies...])
.venv/bin/pip install --requirement requirements.txt
# install dev dependencies seperately, for clarity
AC_MSG_NOTICE([installing dev dependencies...])
.venv/bin/pip install --requirement requirements-dev.txt
AC_OUTPUT