Stand Alone Erlang on otp_src_R9C-2

[yerl@REDACTED]

Hi mark!
Great! It works like a charm
Regards,
/Yerl


----Message d'origine----
>Date: Fri, 09 Jul 2004 18:01:32 -0400
>De: Mark Scandariato <mscandar@REDACTED>
>A: erlang-questions@REDACTED
>Sujet: Re: Stand Alone Erlang on otp_src_R9C-2
>
>Turns out you have to supply all the arguments, just so:
>
>elink -t unix -d -o ecat -S ecat -m ecat.beam ...
>
>and the module specifed via -S must have a start/1 to accept the command line arguments:
>start([_|Args]) ->
>	....
>(Args is a list of <<"arg">>)
>Mark.
>
>yerl@REDACTED wrote:
>> Hi All!
>> I'm wondering if there exist a simple way to configure my SAE in the last erlang release.
>> Ecc, ear and esh works fine but not elink.
>> 
>> Mark Scandariato got the same problem in a previous message:
>> http://www.erlang.org/ml-archive/erlang-questions/200404/msg00191.html
>> 
>> This is an example of output error:
>> elink -o ecat -m ecat erlang erl_open_port -s ecat main
>> Cannot parse arguments:["-o",
>>                         "ecat",
>>                         "-m",
>>                         "ecat",
>>                         "erlang",
>>                         "erl_open_port",
>>                         "-s",
>>                         "ecat",
>>                         "main"]
>> Usage:
>>   elink -t [windows | unix] [-d | -s] -o out[.exe]
>>         -S mod -m m1.beam m2.beam m2.beam ...
>> 
>> elink seems to be not able to parse arguments correctly.
>> Could you please give me some help?
>> 
>> cheers
>> /yerl
>> 
>
>