Build an app for Erlang

It's easy to build your own app in Erlang, and you can customize the app yourself, but it's just a simple record of typical practices under Erlang.
That is to build the OTP application.
Build custom A application can be Xxx.app file, you can put the app file in config folder
Eg:config/gs.app
First look at the app file:
App files are all called application resource file

Used to specify the purpose of application && how to start ...

[CPP]View PlainCopy

2. {application,"app name",
4. [
6. {description,"app description"},
8. {VSN,"version number"},
10. {ID, Id},%%app ID with Erl-id ID
12. {Modules,[modules]},%%app contains the module that the SysTools module uses to generate script, tar files
14. {maxp,num},%% Process Maximum value
16. {Maxt,time},%%app run-time unit milliseconds
18. {registered,[mod]},%% Specifies the app name module, SysTools is used to resolve name collisions
20. {included_applictions, [xx]},%% Specifies the child app, loads only, but does not start
22. {applictions,[xxxx]},%% launches your app before it starts, the app will start this list first
24. {env,[xxxx]},%% Configure the app's env, you can use application:get_env to get
26. {mod,{xxx,args}},%% Specifies the app launch module, parameters, corresponding to your app's application behavior
28. {start_phases,[{xxx,xxx}]]%% Specifies some actions for the start phase, corresponding to the OTP application Start_phase function
30. ]
32. }

Customize the app files to your needs, here my app files are:

[CPP]View PlainCopy

2. {
4. Application, GS,
6. [
8. {description, "Just GS."},
10. {VSN, "1.0a"},
12. {modules, [Gs_app,gs_sup]},
14. {registered, [Gs_sup]},
16. {mod, {gs_app, []}},
18. {APPLICTIONS,[KERNEL,STDLIB,SASL]},
20. {env,[{author,"JJ"}]},
22. {start_phases, []}
24. ]
26. }.

OK, next to the custom OTP application:
and put the code file under SRC.

[CPP]View PlainCopy

2. %%src/gs_app.erl
4. -module (Gs_app).
6. -behaviour (application).
8. -export ([start/2,start/0, STOP/1]).
12. Start ()
14. Application:start (GS).
18. Start (_, [])
20. Io:format ("GS start ... ~n"),
22. {OK, Pid} = Gs_sup:start_link (),
24. Io:format ("GS Main PID is ~p ~n", [PID]),
26. {OK, Pid}.
30. Stop (_state),
32. Io:format ("GS stop ... ~n").

One of the gs_sup here is in the app registered module, a typical OTP in supervisor, of course, you can also implement a module ...

[CPP]View PlainCopy

1. %%SRC/GS_SUP.ERL  
2. -module (gs_sup) .  
3. -behaviour (supervisor).   
4. -export ([START_LINK/0,INIT/1]) .  
5.   
6. start_link ()  ->  
7.      supervisor:start_link ({local,? module}, ? Module, []).   
8.   
9.   
10. init ([])  - >   
11.     {ok, {     
12.             {one_for_one, 3, 10 },     
13.              []           
14.      }}.   

To do this, you can simply write a emakefile to implement Erl-make, and put the beam file
Output to Ebin folder

[CPP]View PlainCopy

1. {["src/*"]
2. , [
3. {OutDir, "./ebin"}
4. ]
5. }.

OK, basically, in order to manage the need, you can simply write a script file to launch the app, under Windows
You can do this:

[CPP]View PlainCopy

1. Start.bat
2. CD config/
3. Erl-pa. /ebin/-name [email protected]-setcookie abc-boot start_sasl-s gs_app start
5. Cmd

Finally execute the bat file ...
The app is running and can be application:loaded_applications ().

[CPP]View PlainCopy

2. GS start ....
4. GS Main Pid is <0.48.0>
8. =progress report==== 28-dec-2012::15:51:46 = = =
10. Application:gs
12. STARTED_AT: [Email protected]
14. Eshell V5.9 (abort with ^g)
16. ([email protected]) 1>
20. Eshell V5.9 (abort with ^g)
22. ([email protected]) 1> application:loaded_applications ().
24. [{kernel,"ERTS CXC 138","2.15"},
26. {SASL,"SASL CXC 138","2.2"},
28. {GS,"just GS.","1.0a"},
30. {stdlib,"ERTS CXC 138","1.18"}]
32. ([email protected]) 2>

In this way, the simple app is complete ....
Of course, it's just a very, very simple app. Only the parent supervisor is implemented.

Build an app for Erlang