We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
$ elixir --version Erlang/OTP 26 [erts-14.0.2] [source] [64-bit] [smp:16:16] [ds:16:16:10] [async-threads:1] [jit:ns] [dtrace] Elixir 1.15.7 (compiled with Erlang/OTP 26)
any
The "mix help release" clearly states the target app structure contains "include" folders, but the actual release assemble code doesn't copy it. This line in the code https://github.com/elixir-lang/elixir/blame/7d04c40fc09696f0180baef6b088da87234afd0c/lib/mix/lib/mix/release.ex#L71 shows that only "priv" dirs are copied. Having "include" in the release is important for troubleshooting issues when we need to import records defined in header files, for example.
The mix release is expected to copy applications' include folders as per the documentation.
mix release
include
The text was updated successfully, but these errors were encountered:
4cac7af
Include both priv and include in releases, closes #13145
d716bc2
No branches or pull requests
Elixir and Erlang/OTP versions
Operating system
any
Current behavior
The "mix help release" clearly states the target app structure contains "include" folders, but the actual release assemble code doesn't copy it. This line in the code https://github.com/elixir-lang/elixir/blame/7d04c40fc09696f0180baef6b088da87234afd0c/lib/mix/lib/mix/release.ex#L71 shows that only "priv" dirs are copied.
Having "include" in the release is important for troubleshooting issues when we need to import records defined in header files, for example.
Expected behavior
The
mix release
is expected to copy applications'include
folders as per the documentation.The text was updated successfully, but these errors were encountered: