BINETIX NETWORK

The MAKE_APP extensions are compiled Erlang modules invoked by the main tool-set controller to provide new configuration commands, parameters and other configuration properties. These modules must be deployed in the same directory where MAKE_APP is installed and called from the  command line.

The extensions are invoked by their module names in accordance with the following naming convention: make_app_<extension>.

The extensions are not available for usage by default - you have to explicitly activate them with {include, <extension>}. configuration element. For example, to activate make_app_erlang.beam extension you have to add into your configuration {include, erlang}. element.

•make_app_files

•make_app_erlang

To develop and deploy your own extension for MAKE_APP tool-set is fantastically simple:

1)Create an Erlang source code file from the Extension template provided below;

2)Implement the command handler on_command/2;

3)Compile the extension.

For example: $ erlc make_app_extension.erl

4)Copy the compiled binary into the deployment directory of MAKE_APP tool-set.

5)Add {include, extension}. element to your configuration file.

-module(make_app_extension).
%-behaviour(make_app).       % Optional attribute to validate the make_app behaviour
-export([on_command/2]).     % Required by the make_app controller
-author("Your Name").
-vsn(1.0).
 

-export_commands([cmd_1]).   % Select the commands to the MAKE_APP controller

 
on_command(Command, Params) when is_atom(Command), is_map(Params) -> case Command of
  cmd_1 -> process_cmd_1(maps:get(task, Params));
  _     -> skip
end.
 
process_cmd_1(_Task) -> ok.

Let's make a simple extension, named cleaner, that is going to delete all unnecessary files and directories from your solution.

1)Create and edit a new file named "make_app_cleaner.erl" with your favorite editor.

2)Add the following source code:

-module(make_app_cleaner).
-behaviour(make_app).
-export([on_command/2]).
-import(make_app, [print/2]).
-author("Your Name").
-vsn(1.0).
 
-export_commands([clean_files]).
 
on_command(Command, Params) when is_atom(Command), is_map(Params) -> case Command of
  clean_files -> process_task_clean(maps:get(task, Params));
  _           -> skip
end.
 
process_task_clean(Task) -> [delete(Cmd, Src) || {Cmd, Src} <- maps:get(params, Task, []), is_atom(Cmd), is_list(Src)].
 
delete(files, Mask) -> begin
  Files = filelib:wildcard(Mask),
  [delete(file, F) || F <- Files]
end;
 
delete(file, Name) -> case file:delete(Name) of
  ok -> print("   # File ~p... deleted", [Name]);
  _  -> print("   ! File ~p... skipped", [Name])
end;
 
delete(dir,  Name) -> case file:del_dir(Name) of
  ok -> print("   # Directory ~p... deleted", [Name]);
  _  -> print("   ! Directory ~p... skipped", [Name])
end;
 
delete(Cmd, _) -> {Cmd, skip}.

3)Compile the extension:

$ erlc make_app_cleaner.erl

4)Copy the compiled binary make_app_cleaner.beam into the deployment directory of MAKE_APP tool-set.

5)Update your make_app.config file in order to use your new extension with the following configuration elements:

{include, cleaner}.
{task, clean, #{command => clean_files, call => [compile, release, build, deploy]}}.

Done!

From now on you can use inside your projects the new task "clean" with list of parameters like:

tasks => [
  {clean, [
    {files, "ebin/*.beam"},
    {files, "logs/*.log"},
    {dir,   "doc"}
  ]}
]