forked from erlang/signerl
TCAP: don't depend on the sccp application
First of all, different SCCP implementations may have different names. Secontly, the TCAP application can be started without SCCP. It's only needed when the adaptor process between tcap_tco_server and SCCP is created. This is an explicit action by the user anyway...
This commit is contained in:
parent
665aacb35b
commit
9d04bb6e40
|
@ -8,6 +8,7 @@
|
|||
component_cordinator_sup, component_cordinator,
|
||||
invocation_sup, invocation_fsm]},
|
||||
{registered, []},
|
||||
{applications, [kernel, stdlib, sccp]},
|
||||
%{applications, [kernel, stdlib, sccp]},
|
||||
{applications, [kernel, stdlib]},
|
||||
{env, [{supref, {local, tcap_sup}}]},
|
||||
{mod, {tcap_app, []}}]}.
|
||||
|
|
Loading…
Reference in New Issue