Skip to content
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

respect REBAR_BARE_COMPILER_OUTPUT_DIR env var during descriptor compilation #205

Merged
merged 1 commit into from
Apr 17, 2021
Merged

respect REBAR_BARE_COMPILER_OUTPUT_DIR env var during descriptor compilation #205

merged 1 commit into from
Apr 17, 2021

Conversation

the-mikedavis
Copy link
Contributor

@the-mikedavis the-mikedavis commented Apr 13, 2021

closes #204

this appears to fix my compilation with elixir 1.12

I'm a bit worried that this is just a band-aid fix of some other issue. I can't seem to hunt down what exactly changed in the elixir source that would cause this to be necessary

it looks like rebar recently added support for this environment variable (see erlang/rebar3#2237) which mix started passing to rebar in elixir 1.12

Comment on lines +48 to +57
{filename:join([REBAR_DEPS_DIR, "gpb", "ebin"]),
filename:join([REBAR_DEPS_DIR, "gpb", "test"])};
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please correct me if I'm wrong here about the best way to format this little block: I have no idea what I'm doing with erlang formatting 😅

@the-mikedavis the-mikedavis changed the title always ensure ebin is a directory during descriptor compilation respect REBAR_BARE_COMPILER_OUTPUT_DIR env var during descriptor compilation Apr 13, 2021
@tomas-abrahamsson
Copy link
Owner

It seems to be working fine, I tested just briefly also building with rebar3 and make and rebar2 too (I need to support that still). Nice! Could you squash the commits? (The case statement is fine, orelse in Erlang is short-circuiting (like || in C), whereas plain or is not, but I think both expect booleans as arguments, ie only the atoms true or false, so I think case is better in this case :) )

@the-mikedavis
Copy link
Contributor Author

done and done!

I was fiddling around with an orelse but got some ArgumentErrors I didn't really understand, and it was working in my eshell. I really need to work on my erlang chops, huh? 😁

thanks again for maintaining gpb @tomas-abrahamsson 🙂

@tomas-abrahamsson
Copy link
Owner

Superduper! Looks good, and merged locally.

@tomas-abrahamsson tomas-abrahamsson merged commit abdc6ea into tomas-abrahamsson:master Apr 17, 2021
@tomas-abrahamsson
Copy link
Owner

Included in 4.17.1 which I just pushed. Thanks for the PR!

@the-mikedavis the-mikedavis deleted the elixir-1.12-compilation-fix branch April 17, 2021 19:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

compilation error with elixir 1.12.0-rc.0
2 participants