project-everest / everest

https://project-everest.github.io/
Apache License 2.0
193 stars 29 forks source link

Karamel build breaking on windows, perhaps .. processing? #102

Open briangmilnes opened 1 year ago

briangmilnes commented 1 year ago

So everest just built for me today on Linux but won't on Windows 11 (under cygwin). The missing file exists so this looks like some kind of .. processing issue.

KaRaMeL auto-detecting tools. Here's what we found: readlink is: readlink KaRaMeL called via: C:\cygwin\home\brian\everest\karamel\src_build\default\Karamel.exe KaRaMeL home is: /home/brian/everest/karamel/krmllib/.. ⚙ KaRaMeL will drive F*. Here's what we found: read FSTAR_HOME via the environment fstar converted to windows path: C:/cygwin/home/brian/everest/FStar/bin/fstar.exe fstar home converted to windows path: C:/cygwin/home/brian/everest/FStar fstar lib converted to windows path: C:/cygwin/home/brian/everest/FStar/ulib fstar is on branch master fstar is: C:/cygwin/home/brian/everest/FStar/bin/fstar.exe /home/brian/everest/karamel/krmllib/../runtime/WasmSupport.fst C:/cygwin/home/brian/everest/FStar/ulib/FStar.UInt128.fst --trace_error --expose_interfaces --include\ /home/brian/everest/karamel/krmllib/../krmllib --include /home/brian/everest/karamel/krmllib/../include Fatal error: exception Sys_error("/home/brian/everest/karamel/krmllib/../misc/Makefile.basic: No such file or directory") make[1]: [Makefile:119: dist/generic/Makefile.include] Error 2 make[1]: Leaving directory '/home/brian/everest/karamel/krmllib' make: [Makefile:36: krmllib] Error 2 make: Leaving directory '/home/brian/everest/karamel'

FAILURE: build failed for karamel

msprotz commented 1 year ago

I don't know that anyone actively maintains developing on windows, but you may have luck by using "hybrid" paths of the form c:/.../.../ (yes, using forward slashes) everywhere, notably for KRML_HOME -- it looks like krml, a windows executable, is trying to access cygwin paths, which don't exist -- using these "hybrid" paths should ensure that the paths work for both the cygwin layer and the windows kernel

briangmilnes commented 1 year ago

Jonathan,

No problem, I have a working Linux build of everything with vscode working. So I'll stick there.

Thanks, Brian

On Wed, Aug 9, 2023 at 10:29 AM Jonathan Protzenko @.***> wrote:

I don't know that anyone actively maintains developing on windows, but you may have luck by using "hybrid" paths of the form c:/.../.../ (yes, using forward slashes) everywhere, notably for KRML_HOME -- it looks like krml, a windows executable, is trying to access cygwin paths, which don't exist -- using these "hybrid" paths should ensure that the paths work for both the cygwin layer and the windows kernel

— Reply to this email directly, view it on GitHub https://github.com/project-everest/everest/issues/102#issuecomment-1671854825, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACKMDK3UHXQSO4ANGUOVWGTXUPCIHANCNFSM6AAAAAA3JO45E4 . You are receiving this because you authored the thread.Message ID: @.***>