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/`.
This commit is contained in:
parent
cd7aca7b45
commit
39fd5a7bf2
3 changed files with 238 additions and 1 deletions
14
configure.ac
14
configure.ac
|
|
@ -1,11 +1,25 @@
|
|||
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
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue