Closed s5bug closed 2 years ago
Hrrm, not sure what the correct behaviour here is. I guess we catch the error and use some "?" version instead.
amuletml > Linking .stack-work\dist\274b403a\build\amc-prove\amc-prove.exe ...
amuletml > Preprocessing executable 'amulet-lsp' for amuletml-1.0.0.0..
amuletml > Building executable 'amulet-lsp' for amuletml-1.0.0.0..
amuletml > [ 1 of 10] Compiling AmuletLsp.Features
amuletml > [ 2 of 10] Compiling AmuletLsp.Diagnostic
amuletml > [ 3 of 10] Compiling AmuletLsp.Features.Folding
amuletml > [ 4 of 10] Compiling AmuletLsp.Features.Outline
amuletml > [ 5 of 10] Compiling AmuletLsp.Features.TypeOverlay
amuletml > [ 6 of 10] Compiling AmuletLsp.NameyMT
amuletml > [ 7 of 10] Compiling AmuletLsp.Worker
amuletml > [ 8 of 10] Compiling AmuletLsp.Loop
amuletml > [ 9 of 10] Compiling Version
amuletml > [10 of 10] Compiling Main
amuletml >
amuletml > <no location info>: error:
amuletml > .git/logs/HEAD: openBinaryFile: does not exist (No such file or directory)
amuletml >
Progress 89/90
-- While building package amuletml-1.0.0.0 (scroll up to its section to see the error) using:
F:\Win\Stack\setup-exe-cache\x86_64-windows\Cabal-simple_Z6RU0evB_3.2.1.0_ghc-8.10.4.exe --builddir=.stack-work\dist\274b403a build --ghc-options " -fdiagnostics-color=always"
Process exited with code: ExitFailure 1
Ahh, dammit. It hadn't occurred to me that addDependentFile
would need it to have the file exist.
stack.yaml:
package.yaml:
stack run
on a new example project with these dependencies gives:For more context: I'm attempting to use amuletml as a dependency because I want to parse a type definition file that looks like
and generate a C++ header that looks like
and I am guessing that using Haskell with Amulet as a dependency is the easiest way to accomplish this.