Re: lang/elixir | v1.13.3

Hi,



For us the difference is that the runtime does not come erl or the erlang compiler. We run a custom developed app written in Elixir but there are some erlang modules as well, recompiling said app requires the files found in the "erland24" pot but not in "erlang-runtime24". I Hope that makes things a bit clearer. Basically the way the non -devel elixir port works.



Thanks.






---- On Wed, 16 Feb 2022 17:03:03 -0500 Dave Cottlehuber <dch@freebsd.org> wrote ----



>> One issue i have with the port, it wants the erlang runtime, but we need the full erlang for our use. Any suggested actions (an option to choose would be nice, i don't want to manually edit your Makefiles)? 
 
Hi Mike, 
 
there is no difference (other than OTP version) between: 
 
erlang 
erlang-runtime21 
erlang-runtime22 
erlang-runtime23 
erlang-runtime24 
 
lang/erlang *is* erlang-runtime24 atm. 
 
Or do you mean, you need erlang-wx, java etc as well? 
 
You can re-target the port with ERLANG_VER= ... something else, or 
modify the post-patch target not to be version-specific. 
 
The reason for this apparent hack is that OTP24 compiled beam files 
are not compatible with OTP21 beam file opcodes any more. So we 
need to make sure that people who want JIT-enhanced OTP run with 
the OTP release that we built against, and that people like me 
who run multiple erlang-derived apps, each embed the path internally. 
 
A+ 
Dave 
 





Mike Jakubik

https://www.swiftsmsgateway.com/



Disclaimer: This e-mail and any attachments are intended only for the use of the addressee(s) and may contain information that is privileged or confidential. If you are not the intended recipient, or responsible for delivering the information to the intended recipient, you are hereby notified that any dissemination, distribution, printing or copying of this e-mail and any attachments is strictly prohibited. If this e-mail and any attachments were received in error, please notify the sender by reply e-mail and delete the original message.