[rabbitmq-discuss] Building addins on Windows

Sun Jul 24 17:03:32 BST 2011

Hi, I'm having some issues building the shovel addin on Windows under
cygwin. I am following the instructions in the README of the addin, cloning
the umbrella project and the others below it (I think the addin requires
erlando as well, which is not documented).
I can build the rabbitmq-erlang-client just fine, but erlando and server
fail, which prevent me from building the shovel addin. The problem seems to
be related to escript (I'm invoking my Windows erlang installation as it
appears Erlang won't build under cygwin), and not the one related to
appending .exe when invoking it since I patched the scripts to do that
already.
When invoking escript.exe from the win command line it works, while invoking
it from cygwin always gives "Failed to open file ...". It looks like escript
windows version doesn't play nice with cygwin.
That said, if I didn't have to build server and erlando I may be able to
build the shovel addin, but I could not figure out how to point it to my
existing server binaries.

On Sun, Jul 24, 2011 at 14:01, Simone Busoli <simone.busoli at gmail.com>wrote:

> Thanks Emile, so I'll just need to build the plugin itself if I don't need
> to change the server, right?
> And building the plugin, the shovel in this case, does have any specific
> requirements?
> On Jul 24, 2011 1:48 PM, "Emile Joubert" <emile at rabbitmq.com> wrote:
> > Hi Simone,
> >
> > Op 24/07/11 12:23, het Simone Busoli geskryf:
> >> I would like to try adding a max-hops option to the shovel addin, but I
> have
> >> no past experience in erlang nor in building an addin from the sources.
> I
> >> looked at the docs and I would like to know whether building on Windows
> is
> >> supported and especially if I need to build the server too, or a binary
> >> deployment is enough to modify and test the addin.
> >
> > It is fairly easy to build the broker on Windows if Cygwin is installed.
> > You will need at least GNU Make and have the Erlang compiler and
> > utilities in $PATH. You may want to go this route if you need to modify
> > the broker or if you want to develop against the very latest unreleased
> > version of the broker.
> >
> > If you don't need to modify the broker then dropping your .ez file in
> > the plugins directory of a released build will work. Creating symlinks
> > in the plugins directory as suggested in the plugins development page
> > will not work on Windows.
> >
> > http://www.rabbitmq.com/plugin-development.html
> >
> >
> > -Emile
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110724/a5c63e5c/attachment.htm>