-
-
Notifications
You must be signed in to change notification settings - Fork 238
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
Major relx release 4.0 will no longer be an escript #887
Comments
Thanks for the heads up, I'll experiment when time allows. Probably just call with |
Hi @essen, any update on this? We were looking at moving to OTP24 but we've encountered an issue with Erlang.mk where we can't build because of relx and since relx isn't an escript anymore, I'm not quite sure how to proceed. Is the solution to move away from erlang.mk and to rebar3 for now? |
Was not aware there was an issue with 24, can you be more specific? I will try/fix tomorrow. |
Versions:
Steps:
Issue:It seems to fail at
Running
My git version supports the
Relx Error:
|
This suggests that you are running this in a deep sub directory, which results in file names too long for the operation Relx is trying to do. I'm not sure why going to 24 gives you problems when there were none before. Note that the tests pass just fine on 24 for me (tested just a few minutes ago). Is this Windows by any chance? |
I've updated my above comment with more info @essen Linux, done a bit more digging and looks like relx is using an older version of git from what I can tell - any idea whether relx bundles git inside the release? The only git I have installed supports the
|
Sorry I had not seen the git info when I replied. I am not sure what calls an old git, but it's not bundled with erlang.mk or relx. The caller of the old git is most likely Erlang.mk. You can check the app file for folsom for example and confirm that the Finding where this git program is and removing it might solve your issue. |
@essen did some more digging and think I've found what the problem is - will raise a separate issue to refrain from muddying this one again :) Worthwhile me deleting my comments on this issue do you think? Looks like the same issue as #924 - an issue I raised back in feb 🤦 |
Let's keep all the context thanks! |
For the record this is done in the Context is at #945 so I'll be closing this ticket. Thanks! |
Opening this to let you know relx won't be usable the same way by erlang.mk in the next major release.
relx 4.0 won't build to an escript anymore but it should still be usable simply by calling into it like erlang.mk already does for some other tasks with
erl
.Another option would be creating a small escript wrapper.
Or I could see about adding a
bare release
task to rebar3 that doesn't do any of the other rebar3 shit and just calls relx with the args/config needed for erlang.mk to work.The text was updated successfully, but these errors were encountered: