You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two executables named enso among the daily bits we produce. That's confusing and we shall fix it.
One of them is called Enso launcher. To learn about it, please visit our download page: https://github.com/enso-org/enso/releases/tag/2024.1.1 - the download is in section called Enso Engine on that page, but in fact, it is not the engine, it is the launcher!
To learn more abou tthe enso launcher visit this documentation page - it contains nice description of the whole universtal launcher/updater picture...
we need to find a better location for exposing native image built launcher. The idea is to rename the launcher to ensoup:
It is a nice, illustrative name derived from the rustup example that nicely describes one of the purposes of ensoup - download the distributions of Enso automatically. Once the enso in the bundle is renamed to ensoup, we can proceed with placing a native image built binary next to it under the name enso - but that's for a different PR.
The text was updated successfully, but these errors were encountered:
the executable seems to work to some extend. I can ensoup new path_to_a_project and it runs. I haven't tested the other functionality (CCing @radeusgd), but in general things seem to work.
I haven't tested the other functionality (CCing @radeusgd), but in general things seem to work.
I have downloaded the Windows bundle.
Seems to work OK to me. I've checked most of the functionality, incl. the installation feature and all seem to work as expected. I have only not checked the self-upgrade.
There are two executables named
enso
among the daily bits we produce. That's confusing and we shall fix it.One of them is called Enso launcher. To learn about it, please visit our download page: https://github.com/enso-org/enso/releases/tag/2024.1.1 - the download is in section called Enso Engine on that page, but in fact, it is not the engine, it is the launcher!
To learn more abou tthe enso launcher visit this documentation page - it contains nice description of the whole universtal launcher/updater picture...
However to benefit from the work done by
we need to find a better location for exposing native image built launcher. The idea is to rename the launcher to
ensoup
:It is a nice, illustrative name derived from the
rustup
example that nicely describes one of the purposes ofensoup
- download the distributions of Enso automatically. Once theenso
in the bundle is renamed toensoup
, we can proceed with placing a native image built binary next to it under the nameenso
- but that's for a different PR.The text was updated successfully, but these errors were encountered: