A plugins for rebar3 to generate a compatible mix.exs file and Elixir bindings.
This plugin has two commands :
rebar3 elixir generate_mix
will generate the Mix file.rebar3 elixir generate_lib
will generate Elixir bindings.
## Usage
rebar3_elixir is available has a hex or git dependency :
Juste add :
{plugins, [rebar3_elixir]}.
or
{plugins, [
{rebar3_elixir, {git, "https://github.com/botsunit/rebar3_elixir.git"}}
]}.
in your rebar.config
.
% rebar.config
{erl_opts, [debug_info, warn_export_vars, warn_shadow_vars, warn_obsolete_guard]}.
{plugins, [rebar3_elixir]}.
{elixir_version, "~> 1.2"}.
{deps, [
{lager, "~> 3.2"},
{erlydtl, ".*", {git, "https://github.com/erlydtl/erlydtl.git", {branch, "master"}}}
]}.
% test.app
{application, test,
[
{description, ""},
{vsn, "0.0.1"},
{registered, []},
{modules, []},
{applications, [
kernel,
stdlib,
syntax_tools,
compiler,
goldrush,
lager
]},
{mod, {test_app, []}},
{env, []}
]}.
rebar3 elixir generate_mix
will generate :
defmodule Test.Mixfile do
use Mix.Project
def project do
[
app: :test,
version: "0.0.1",
elixir: "~> 1.2",
build_embedded: Mix.env == :prod,
start_permanent: Mix.env == :prod,
deps: deps
]
end
def application do
[
applications: [:syntax_tools, :compiler, :goldrush, :lager],
env: [],
mod: {:test_app, []}]
]
end
defp deps do
[
{:lager, "~> 3.2"},
{:erlydtl, ~r/.*/, git: "https://github.com/erlydtl/erlydtl.git", branch: "master"},
]
end
end
rebar3 elixir generate_lib
will generate an Elixir module in lib
for each Erlang module. For example :
- From
src/example.erl
,rebar3_elixir
will generate a modulelib/Example.ex
- From
src/my_example.erl
,rebar3_elixir
will generate a modulelib/My.Example.ex
- From
src/other/simple_example.erl
,rebar3_elixir
will generate a modulelib/Other.Simple.Example.ex
You specify the modules for which you want a binding, by using the elixir_bindings
option :
{elixir_bindings, [example, simple_example]}.
In this case, only lib/Example.ex
and lib/Other.Simple.Example.ex
will be generated.
You can specify a list of function to include or exclude :
{elixir_bindings, [{example, [{only, [fun1, {fun2,2}]}]}]}.
Here, only fun1
(with any arity) and fun2/2
will be availables in the binding lib/Example.ex
.
{elixir_bindings, [{example, [{except, [fun1, {fun2,2}]}]}]}.
Here, every function from the module example
, except fun1
(with any arity) and fun2/2
, will be availables in the binding lib/Example.ex
.
You can also add a prefix by using elixir_bindings_prefix
:
{elixir_bindings_prefix, hello}.
If you want to force the Elixir module name, you can use the as
option :
{elixir_bindings, [{example, [{as, "My.Module.Name"}]}]}.
So rebar3_elixir
will generate lib/Hello.Example.ex
and lib/Hello.Other.Simple.Example.ex
Copyright (c) 2016, Bots Unit
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.