cabal.project

packages:
  .

package cooked-validators
  coverage: True
  library-coverage: True
  
package cardano-crypto-praos
  flags: -external-libsodium-vrf

-- Custom repository for cardano haskell packages
-- See https://github.com/IntersectMBO/cardano-haskell-packages
-- on how to use CHaP in a Haskell project.
repository cardano-haskell-packages
  url: https://chap.intersectmbo.org/
  secure: True
  root-keys:
    3e0cce471cf09815f930210f7827266fd09045445d65923e6d0238a6cd15126f
    443abb7fb497a134c343faf52f0b659bd7999bc06b7f63fa76dc99d631f9bea1
    a86a1f6ce86c449c46666bda44268677abf29b5b2d2eb5ec7af903ec2f117a82
    bcec67e8e99cabfa7764d75ad9b158d72bfacf70ca1d0ec8bc6b4406d1bf8413
    c00aae8461a256275598500ea0e187588c35a5d5d7454fb57eac18d9edb86a56
    d4a35cd3121aa00d18544bb0ac01c3e1691d618f462c46129271bccf39f7e8ee

index-state:
  , hackage.haskell.org 2025-03-17T12:01:29Z
  , cardano-haskell-packages 2025-04-04T13:50:31Z
  
-- We never, ever, want this.
write-ghc-environment-files: never

-- The only sensible test display option, since it allows us to have colourized
-- 'tasty' output.
test-show-details: direct

-- These packages appear in our dependency tree and are very slow to build.
-- Empirically, turning off optimization shaves off ~50% build time.
-- It also mildly improves recompilation avoidance.
-- For dev work we don't care about performance so much, so this is okay.
package cardano-ledger-alonzo
  optimization: False
package ouroboros-consensus-cardano
  optimization: False
package cardano-api
  optimization: False
package cardano-crypto-praos
  flags: -external-libsodium-vrf

constraints:
  cardano-api ^>= 10.13,

source-repository-package
    type: git
    location: https://github.com/tweag/cardano-node-emulator-forked
    tag: 2c7bfc7663956d3ecccff3243ca65f38a5526a2c
    subdir:
      plutus-script-utils
      plutus-ledger
      cardano-node-emulator
      freer-extras