You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix cross-compilation compatibility and ob-run reliability
The cabal.project used a flat package list that included packages with
build-type: Custom depending on obelisk-setup. When the WASM/GHCJS
cross-compiler's cabal resolved the project, it could not find
obelisk-setup (only available in the native ghc-pkg), causing
cross-builds to fail.
Move backend, frontend/js, frontend/wasm, and static/generated/custom
behind an `if !(arch(javascript) || arch(wasm32))` conditional so the
cross-compiler's cabal never attempts to resolve their setup-depends.
Add obelisk-setup as a build-depends of obelisk-generated-static-custom
so it appears in ghc-pkg for native cabal's setup-depends resolution.
Guard frontendDataOverride and backendDataOverride with
mkOptionalPackages so they are silently skipped in cross projects where
those packages do not exist, fixing an infinite recursion during nix
evaluation of projectCross.
Fix ob-run's `cabal list-bin` returning the wrong path under -O0 by
emitting cabal-level optimization flags (-O0) instead of
--ghc-options=-O0, and passing only optimization flags (not the full
extraFlags with --ghc-options) to list-bin/assembleAndLinkFrontend/
linkFrontendAssets.
Fix ob-run EXIT trap to also kill inotifywait and read processes.
Remove unused dependencies (directory from frontend, filepath from
backend library).
0 commit comments