-
Notifications
You must be signed in to change notification settings - Fork 326
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build script switch to generate either shell xor binary for bin/enso
#12014
Comments
Pavel Marek reports a new STANDUP for today (2025-01-13): Progress: - Discussion about project-private types.
|
Pavel Marek reports a new STANDUP for today (2025-01-14): Progress: - DevX improvement to IR dumper: #12056
|
Pavel Marek reports a new STANDUP for today (2025-01-15): Progress: - Idea: Dump compiler IR graphs to IGV format - #12061 It should be finished by 2025-01-18. |
Pavel Marek reports a new STANDUP for today (2025-01-16): Progress: - The PR merged.
|
Fixes another issue related to #12014 - `runEngineDistribution` has to generate _native image_ launchers when in `ENSO_LAUNCHER=native` mode. This PR also introduces additional comma separated values to the `ENSO_LAUNCHER` variable: - `shell` uses shell launchers and has no additional sub options - `native` generates some form of _native image_ launchers - concatenations are possible: - `fast,native` disables code optimizations to speed the build up - `test,native` enables assertions - `debug,native` enables debug information - combinations up to `native,test,debug,fast` are also possible
The instant launching of Enso programs discussion describes needs for:
All these requests have one in common:
buildEngineDistribution
that generates shell launchersengine-runner/buildNativeImage
that adds/overridesbin/enso
orbin/enso.exe
engine-runner/buildNativeImage
The Switch
An environment variable would be a good switch and would play well with the CI as the case of ENSO_JAVA shows. Let's thus introduce
ENSO_LAUNCHER
which can have following valuesnative
debugnative
shell
based on these values it either executes the current copy of shell launchers or it skips this behavior and invokes
engine-runner/buildNativeImage
instead. Thedebugnative
variant shall include-ea
flag when invokingnative-image
- a mode needed for running Enso tests.After the change it should be possible to:
and see either only
enso
Unix executable orenso.exe
on Windows.Notes
ENSO_LAUNCHER
remainsshell
for now - e.g. release behavior remains unchagedENSO_LAUNCHER=debugnative
variable instead of invokingengine-runner/buildNativeImage
directlyThe text was updated successfully, but these errors were encountered: