Replies: 5 comments 6 replies
-
I guess part of the issue is that the beam files are flat in ebin/ but the source files are not searched recursively by systools whereas rebar3 will do so. |
Beta Was this translation helpful? Give feedback.
-
I am having a similar issue and I am not sure if there is a solution being presented that I am being too dense and missing. I am working on an opensource tool that will allow starting from a database schema, and then generate protobuffers and all the CRUDL (Create, Read, Update, Delete, List/Lookup) code. The tool then ties in with In my case, the tool repo was generated with Everything compiles but does not run. My issue is a little more extensive:
Note, the same is true for Here is my rebar3.config
When I investigate the I am using
and
The other thing that stands out is Here is the debug output... Any help is much appreciate. Thanks! |
Beta Was this translation helpful? Give feedback.
-
we don't have anything to offer at this point -- none of the maintainers recently had time to solve this one yet. Thanks for the additional information though. No idea yet when I'll have the time to take a look, unfortunately, but the extra data will likely be useful. |
Beta Was this translation helpful? Give feedback.
-
I have a similar (the same?) issue. I have just upgraded from rebar3 v3.9.1 to rebar3 v3.15.2 (for the hex.pm TLS fix). With no other changes to OTP version (21). rebar.config or the relx.config (we use a separate file and run rebar3 release -c relx.conf) we now get these same "Source code not found" warnings. The files it is complaining about all all external deps and the src tree/folder structure for these has not changed (they're pinned). So.. it feels like something has changed in the defaults or behaviour of rebar3/relx to trigger these warnings? The relx.config is minimal (replaced app names with X, Y, and Z), e.g.
As you can see, it has no explicit "mode" specified, nor any of the things that mode is expanded to by relx (include_src, debug_info, include_erts, dev_mode). Inspecting our previous releases, they appears to be the result of "{mode, dev}" or equivalent. In addition to these new warnings, the relx.config above is no longer valid. default_release - no longer supported? (but still documented here https://github.com/erlware/relx/wiki/Configuration) release tuple, applications list, format of applications WRT required version changed from "X>=0.3.4" to {X, "0.3.4"} (and I cannot see whether >= is still supported in some form?) |
Beta Was this translation helpful? Give feedback.
-
I have some test result about it
flow:
default config:
when I remove otp(right?), it can work:
release warning:
tar warning:
it can work with recursive dir in |
Beta Was this translation helpful? Give feedback.
-
I am trying to upgrade to the latest version of rebar3, but I am getting following messages during release:
I found out that this warning comes from https://github.com/erlang/otp/blob/OTP-21.3/lib/sasl/src/systools_make.erl#L1151
And may be caused be prometheus lib structure:
https://github.com/deadtrickster/prometheus.erl/tree/v4.6.0/src
My question is it a problem with prometheus lib, with my rebar config or something else? How can I fix this warning?
I reproduced it with bare umbrella project:
Beta Was this translation helpful? Give feedback.
All reactions