[erlang-questions] reltool not copying erl_interface

[Tim Watson]

Can't shed any light on the reltool issue, but if you're customising your
rebar build, you should probably just use a plugin instead of a customised
rebar binary. A plugin makes this very simple (and can be distributed
across multiple projects if you package it as a mini-library).

-module(fix_rel_plugin).
-export([post_generate/2]).

post_generate(Config, _) ->
    Path = code:lib_dir(erl_interface),
    rebar_file_utils:cp_r(Path,
        filename:join([rebar_utils:get_cwd(), "myproject", "lib",
            filename:basename(Path)])),
    ok.

%% rebar.config
{plugins, [fix_rel_plugin]}.

At least until reltool gets fixed or the problem better diagnosed you don't
have to maintain a custom rebar fork/branch that way.

On 4 December 2011 20:06, Jesse Gumm <gumm@REDACTED> wrote:

> Hi,
>
> I realize, of course, that I can do workarounds to this issue (and so
> far my workaround has been a modified rebar), but my concern is that I
> believe this *should* be something that is properly handled by
> reltool, at the very least when using {profile,development}.
>
> Anyone else can shed some light on this?
>
> -Jesse
>
> On Sun, Dec 4, 2011 at 1:46 AM, Dmitry Kolesnikov
> <dmkolesnikov@REDACTED> wrote:
> > Hello Jesse,
> >
> > I've been using GNU auto tools to manage and build erlang projects. It
> gives you a flexibility to mix both erlang and native code. In terms of
> release management, systools is not flexible as I wish thus a two pass
> processing of tar ball is required but this is straight forward with GNU
> make.
> >
> > - Dmitry
> >
> > On 3.12.2011, at 23.05, Jesse Gumm <sigmastar@REDACTED> wrote:
> >
> >> Hello everyone,
> >>
> >> This is a followup to a post I made a few months ago[1], which was
> >> probably too and meandering for anyone to read (I struggle with
> >> brevity).
> >>
> >> The short version is that for the life of me, I cannot find a way to
> >> force the erl_interface dir to get copied with reltool.
> >>
> >> There are reltool options for forcing an app to get copied, but
> >> erl_interface isn't an app (ie, doesn't have a .app file).
> >>
> >> Anyone have any thoughts on this?
> >>
> >> Thanks in advance,
> >>
> >> -Jesse
> >>
> >> [1]
> http://erlang.org/pipermail/erlang-questions/2011-October/061923.html
> >>
> >> --
> >> Jesse Gumm
> >> Sigma Star Systems
> >> 414.940.4866
> >> gumm@REDACTED
> >> http://www.sigma-star.com
> >> _______________________________________________
> >> erlang-questions mailing list
> >> erlang-questions@REDACTED
> >> http://erlang.org/mailman/listinfo/erlang-questions
>
>
>
> --
> Jesse Gumm
> Sigma Star Systems
> 414.940.4866
> gumm@REDACTED
> http://www.sigma-star.com
> _______________________________________________
> 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/20111204/ed04cc86/attachment.htm>