Skip to content

works. More to do: why was pip used rather than conda? ask before mod… #985

works. More to do: why was pip used rather than conda? ask before mod…

works. More to do: why was pip used rather than conda? ask before mod… #985

Workflow file for this run

name: smoke test
on:
# Runs on pushes targeting the default branch
push:
branches-ignore:
- master
# branches: ['develop']
pull_request:
branches: ['main']
# Allows you to run this workflow manually from the Actions tab
workflow_dispatch:
# Default to bash
defaults:
run:
shell: bash
jobs:
build:
strategy:
fail-fast: false
matrix:
os:
- name: 'ubuntu-22.04'
- name: 'macos-latest'
- name: 'windows-latest'
# cmd_extra: '-win'
env: ['py310', 'py311', 'py312', 'py313']
runs-on: ${{ matrix.os.name }}
steps:
# checkout repo
- uses: actions/checkout@v2
# set up pixi
- uses: prefix-dev/setup-pixi@v0.8.1
with:
environments: ${{ matrix.env }}
pixi-version: v0.39.5
manifest-path: pixi/pixi.toml
# On macOS, the conda-forge cross-compiler (arm64-apple-darwin20.0.0-clang)
# requires SDKROOT/CONDA_BUILD_SYSROOT to link against libSystem.dylib.
# Without this, meson's C compiler sanity check fails on newer Xcode versions
# (e.g. Xcode 26+) because dyld rejects executables missing LC_LOAD_DYLIB.
# MACOSX_DEPLOYMENT_TARGET=11.0 matches the compiler's darwin20 target triplet.
- name: Set macOS SDK paths
if: runner.os == 'macOS'
run: |
SDKROOT=$(xcrun --sdk macosx --show-sdk-path)
echo "SDKROOT=$SDKROOT" >> $GITHUB_ENV
echo "CONDA_BUILD_SYSROOT=$SDKROOT" >> $GITHUB_ENV
echo "MACOSX_DEPLOYMENT_TARGET=11.0" >> $GITHUB_ENV
# run install to see if it works
- name: Build
# run: pixi run --manifest-path pixi/pixi.toml -e ${{ matrix.env }} install${{ matrix.os.cmd_extra }}
run: pixi run --manifest-path pixi/pixi.toml -e ${{ matrix.env }} install
- name: test
run: pixi run --manifest-path pixi/pixi.toml -e ${{ matrix.env }} test