Skip to content

Love that you can't test CI without pushing #75

Love that you can't test CI without pushing

Love that you can't test CI without pushing #75

Workflow file for this run

name: Lint Builds
'on':
push:
branches:
- '**'
paths:
# It would be nice if I could specify this per-job, but I'm not making a whole new file just to avoid running
# clang for web-only changes.
- src/*
- wasm/*
- .clang-format
- .github/workflows/lint-build.yml
workflow_dispatch: ~
jobs:
build-native-mac:
runs-on: macos-latest
strategy:
matrix:
arch:
- x86_64
- aarch64
name: Verify C++ Build with clang on ${{ matrix.arch }}
steps:
- uses: actions/checkout@v4
- name: Invoke clang
shell: bash
run: >+
clang++ -DVERSION=0.0.0 -DNDEBUG -WCL4 -Wnon-gcc -Wimplicit-fallthrough -Werror -std=c++14 -o /dev/null
-target ${{ matrix.arch }}-apple-macosx src/*.cpp
build-native-windows:
runs-on: windows-latest
name: Verify C++ Build with MSVC
steps:
- uses: actions/checkout@v4
- uses: ilammy/msvc-dev-cmd@v1.12.1
- name: Invoke MSVC
shell: pwsh
run: |
cl .\src\*.cpp /EHsc /DVERSION=0.0.0 /DNDEBUG /std:c++20 /MTd /analyze /W4 /WX /we5219
lint-npm:
runs-on: ubuntu-latest
name: Lint with JS Tools
steps:
- uses: actions/checkout@v4
- name: npm lint
shell: bash
run: |
cd wasm
npm ci --no-fund
npm run lint
verify-wasm-build:
runs-on: ubuntu-latest
name: Verify wasm build
steps:
# Largely copied from build-and-deploy-pages.jobs.build-wasm.steps
- uses: actions/checkout@v4
- uses: numworks/setup-emscripten@bbc4f5e15974bc13e69fdadecfd1858ecb1c4dbb
- uses: actions/cache@v3
with:
path: /opt/hostedtoolcache/emscripten/latest/x64/upstream/emscripten/cache/sysroot/lib/wasm32-emscripten/lto
key: libs-${{ hashFiles('~/work/Trilangle/Trilangle/emsdk/upstream/emscripten/system/lib/**.c') }}
restore-keys: "libs-\n"
- name: Run build script
shell: bash
run: |
cd wasm
npm ci --omit dev --no-fund
./build_wasm.sh lint