[erlang-questions] exmpp and rebar

[Tim Watson]

You don't need rebar-ized versions of things to make them work in a
release.

When you say the beam is laying next to the .app file, do you mean in the
generated release directory structure, or in the original install location
(inside of code:lib_dir), because those are two different things and
sometimes reltool (upon which `rebar generate' is based) doesn't copy beams
across for a number of reasons.

On 2 November 2011 09:07, Max Bourinov <bourinov@REDACTED> wrote:

> Already tried yours :-) Doesn't work somehow...
>
> Did you manage to make it running as a part of bigger rebar-ized app?
>
>
>
> On Wed, Nov 2, 2011 at 12:03 PM, Paul Oliver <puzza007@REDACTED> wrote:
>
>> Hi Max,
>> I have a quick and dirty rebarised version of exmpp here
>> https://github.com/puzza007/exmpp.
>> Cheers,Paul.
>> On Wed, Nov 2, 2011 at 8:10 AM, CGS <cgsmcmlxxv@REDACTED> wrote:
>> > You need to include the path toward you exmpp or put exmpp into the
>> Erlang
>> > lib standard path. It looks like your application doesn't know from
>> where to
>> > take exmpp.
>> >
>> > Cheers,
>> > CGS
>> >
>> >
>> >
>> > On 11/02/2011 08:54 AM, Max Bourinov wrote:
>> >
>> > Hi guys,
>> > I have rebar-ized project that uses exmpp library. exmpp library
>> installed
>> > in my system (sudo make install).
>> > Since there is no properly rebar-ized exmpp I try to run in in my
>> > application code manually instead of starting it in processor.app:
>> > start(_StartType, _StartArgs) ->
>> > ok = application:start(exmpp),
>> > processor_sup:start_link().
>> > When I test my application (not release) everything work like a charm.
>> > But when I do:
>> > ./rebar compile
>> > ./rebar generate
>> > and then run released node I have the following exception:
>> > Erlang R14B04 (erts-5.8.5) [source] [smp:2:2] [rq:2] [async-threads:5]
>> > [hipe] [kernel-poll:true]
>> >
>> > =INFO REPORT==== 2-Nov-2011::10:38:08 ===
>> >     application: processor
>> >     exited: {bad_return,
>> >                 {{processor_app,start,[normal,[]]},
>> >                  {'EXIT',
>> >                      {{badmatch,
>> >                           {error,{"no such file or
>> > directory","exmpp.app"}}},
>> >                       [{processor_app,start,2},
>> >                        {application_master,start_it_old,4}]}}}}
>> >     type: permanent
>> > {"Kernel pid
>> >
>> terminated",application_controller,"{application_start_failure,processor,{bad_return,{{processor_app,start,[normal,[]]},{'EXIT',{{badmatch,{error,{[110,111,32,115,117,99,104,32,102,105,108,101,32,111,114,32,100,105,114,101,99,116,111,114,121],[101,120,109,112,112,46,97,112,112]}}},[{processor_app,start,2},{application_master,start_it_old,4}]}}}}}"}
>> > Crash dump was written to: erl_crash.dump
>> > Kernel pid terminated (application_controller)
>> >
>> ({application_start_failure,processor,{bad_return,{{processor_app,start,[normal,[]]},{'EXIT',{{badmatch,{error,{[110,111,32,115,117,99,104,32,102,105,1
>> > As I already said this approach doesn't work. Do you have any ideas how
>> to
>> > properly configure my app to use exmpp?
>> > Best regards,
>> > Max
>> >
>> > _______________________________________________
>> > erlang-questions mailing list
>> > erlang-questions@REDACTED
>> > http://erlang.org/mailman/listinfo/erlang-questions
>> >
>> >
>> > _______________________________________________
>> > erlang-questions mailing list
>> > erlang-questions@REDACTED
>> > http://erlang.org/mailman/listinfo/erlang-questions
>> >
>> >
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions
>>
>
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20111102/d10e930b/attachment.htm>