Closed DrYSG closed 4 years ago
Thank you for testing! I don't have a Windows machine unfortunately so not really sure what this is. Would appreciate if anyone could help with this.
@yawaramin what I often try, is after the clone is $ esy cleaup . --- followed by removing the _esy and esy.lock folders. In this case it did not work.
From what I can decypher on the message, it strikes me as an esy issue. Since most other packages work with esy, I wonder if you do something different, or if this would not be a good thing to write up and let the esy developers look into what is going on.
the esy install works for both reweb and for your fullstack-reason example.
Hi @DrYSG it could be something I'm doing but as you can see it is building successfully on Mac and Linux, so I am inclined to think it's a Windows/esy issue...
@yawaramin don't know if this helps, But it seems that your derivative project reweb-fullstack-reason gets further along in the build.
https://github.com/yawaramin/fullstack-reason/issues/3
(I do think it does point to an esy windows issue. Do you think we create an issue at the esy github site?)
I think it would be a good idea to mention this issue in the Discord #native-development channel and see if anyone has ideas. We know for a fact that complex projects like Revery and Onivim are being developed on Esy/Windows, so someone may already have come across this...
Win10, running as admin and esy V 0.6.2, using ADMIN console.