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

As reported in https://github.com/erlang/rebar3/issues/2563 #8

Merged
merged 1 commit into from
Aug 24, 2021

Conversation

ferd
Copy link
Collaborator

@ferd ferd commented Aug 21, 2021

And fixed in erlang/rebar3#2606

Relies on having all relevant libs compiled in the same phase (i.e. all
top-level apps or all deps), with two layers of transitive libraries (exometer + custom)
depending on parse_trans, which is called at runtime during the
compiler phase. If the compiler does not feed dep-level information
and does no runtime analysis of compile time deps, either a_lib or z_lib
will fail to build when b_lib calls parse_trans (depending on sorting order).

And fixed in erlang/rebar3#2606

Relies on having all relevant libs compiled in the same phase (i.e. all
top-level apps or all deps), with two layers of transitive libraries
depending on parse_trans, which is called at runtime during the
compiler phase. If the compiler does not feed dep-level information
and does no runtime analysis of compile time deps, either a_lib or z_lib
will fail to build when b_lib calls parse_trans (depending on sorting order).
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.

2 participants