MarcoTrevisiol
I am releasing a small elixir app with mix release. Since I only need the release to run on a linux machine, I do not need any .bat script. I added the option in mix.exs to only include executable for unix. Yet I am not able to get rid of them.
What I did:
mix new example
cd example
then I added the following line in mix.exs, inside “project” function:
releases: [example: [include_executable_for: [:unix]]],
Finally I run mix release. But when I look inside _build/dev/rel/example I find some .bat scripts
$ find _build/ -name '*.bat'
_build/dev/rel/example/releases/0.1.0/env.bat
_build/dev/rel/example/bin/example.bat
I am running the latest stable release of elixir:
$ mix --version
Erlang/OTP 25 [erts-13.1.5] [source] [64-bit] [smp:2:2] [ds:2:2:10] [async-threads:1] [jit:ns]
Mix 1.17.3 (compiled with Erlang/OTP 25)
Is there any way to not include these .bat script inside the release? Should I do something differently?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Phoenix, LiveView, multimedia pipelines, distributed systems. 400 engineers, Elixir since 2017. Available for hire.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #ai
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
Nicodemus
This is working correctly for me with the same version of Elixir, in that there are no “*.bat” files in my release. Are you sure you removed “_build/dev/rel” after adding that option to “mix.exs”? They might be hanging around from the first time you ran
mix releasebefore adding the option?wojtekmach
You have a typo, change:
This is pretty unfortunate, I’m not sure if we can do much about it though. If Elixir allowed people setting custom release options, which can be very useful for custom tooling, then we should keep that. Or introduce an
:extraoption that would be a place for custom options and then we could warn on typos likeinclude_executable_for.MarcoTrevisiol
Of course, I did not check for any typo!
I do not know if some tool like
mix credoshould be able to inform users about unused configuration, sincemixshould not be allowed to perform such checks.