Closed jecisc closed 6 years ago
Well... Soon this repository will make sense no more... Most of its features were pushed to pillar, where it works on 64bits.
Check @samakhov 's draft tutorial here https://samakhov.github.io/academic-process.html
Ok. I wanted to generate the ESUG website but its makefile fails for me because of this.
Check it again, Esug's website should work with pillar because we have it working on travis. Did you try the travis configuration?
On Mon, Jul 16, 2018 at 11:11 AM CyrilFerlicot notifications@github.com wrote:
Ok. I wanted to generate the ESUG website but its makefile fails for me because of this.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/guillep/ecstatic/issues/21#issuecomment-405188404, or mute the thread https://github.com/notifications/unsubscribe-auth/AArO4iPrYZ5DYzKdVppFoDFKLHiC64zZks5uHFjJgaJpZM4VQw-E .
--
Guille Polito
Research Engineer
Centre de Recherche en Informatique, Signal et Automatique de Lille
CRIStAL - UMR 9189
French National Center for Scientific Research - http://www.cnrs.fr http://www.cnrs.fr
Web: http://guillep.github.io http://guillep.github.io
Phone: +33 06 52 70 66 13
What I did was to clone the repository and to run make
. But it failed because it uses ecstatic which installs a Pharo 32bits and it does not work on linux subsystem. It was, for this reason, I asked if it made sense to move ecstatic to 64bits by default.
I'll just execute the makefile step by step and change the scripts by hand to load the 64bits in my linux subsystem.
I tried to use ecstatic on Linux subsystem of windows but the installation failed because Linux subsystem only supports Pharo 64bits.
What do you think about using Pharo 64bits by default in the installation script? Is there objections?