Skip to content

Fully support installing via pip (#562) #476

Fully support installing via pip (#562)

Fully support installing via pip (#562) #476

Workflow file for this run

name: Publish Documents
# Controls when the workflow will run
on:
# Triggers the workflow only on master
push:
branches: [ master ]
# Allows you to run this workflow manually from the Actions tab
workflow_dispatch:
jobs:
build-and-publish-doc:
runs-on: self-hosted
if: github.event.pull_request.draft == false
steps:
- uses: actions/checkout@v3
with:
ssh-key: ${{ secrets.CI }}
submodules: true
fetch-depth: 0
- name: Build ffi module in Release
run: |
git submodule foreach --recursive git clean -ffdx
git submodule foreach --recursive git reset --hard
source /opt/spack/share/spack/setup-env.sh
spack load [email protected]%[email protected] java@11 [email protected]
source ci-script/prepare-python-environment.sh
mkdir build
cmake -B build -S . -DCMAKE_BUILD_TYPE=Release -DFT_WITH_CUDA=OFF -DFT_WITH_MKL=OFF -DFT_WITH_PYTORCH=OFF
cmake --build build -j
- name: Run Doxygen
run: |
# Doxygen from Spack can't be used together with our Python venv. So run it in this separated step
source /opt/spack/share/spack/setup-env.sh
spack load doxygen+graphviz
doxygen Doxyfile
- name: Build and publish doc
run: |
source /opt/spack/share/spack/setup-env.sh
spack load [email protected]%[email protected] java@11 [email protected]
source ci-script/prepare-python-environment.sh
PYTHONPATH=build:python:$PYTHONPATH mkdocs gh-deploy