<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">
<pre><div class="line" id="LC32">deps/ranch:</div><div class="line" id="LC33"> @mkdir -p <span class="k">$(</span>DEPS_DIR<span class="k">)</span></div><div class="line" id="LC34"> git clone -n -- <a class="moz-txt-link-freetext" href="https://github.com/extend/ranch.git">https://github.com/extend/ranch.git</a> <span class="k">$(</span>DEPS_DIR<span class="k">)</span>/ranch</div><div class="line" id="LC35"> <span class="nb">cd</span> <span class="k">$(</span>DEPS_DIR<span class="k">)</span>/ranch ; git checkout -q <span class="k">$(</span>RANCH_VSN<span class="k">)</span></div></pre>
<br>
Am I to understand that the only way of having the dependencies in
another folder than cowboy/deps is to use Rebar (e.g. if compiling
using the makefile it will always assume that dependencies are in
local deps folder)?<br>
<br>
Would be good to have a target to compile cowboy without
dependencies.<br>
<br>
<br>
On 04/02/2013 20:10, Jeremy Ong wrote:<br>
</div>
<blockquote
cite="mid:CAKD1GY7+fvMOR6PhOz=QGAi8r2T_Obf4gCjaH4hN_=J+hNyw4w@mail.gmail.com"
type="cite">
<div dir="ltr">It is rebar compatible
<div><br>
</div>
<div><a moz-do-not-send="true"
href="https://github.com/extend/cowboy/blob/master/rebar.config">https://github.com/extend/cowboy/blob/master/rebar.config</a><br>
</div>
<div><br>
</div>
<div style="">
I use it with rebar all the time.</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Thu, Jan 24, 2013 at 2:41 PM,
Grzegorz Junka <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:list1@gjunka.com" target="_blank">list1@gjunka.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
I understand the move away from Rebar but I'd like to see
the project to be still Rebar-compatible. Would that be a
problem? Mainly I am thinking about dependencies. The Cowboy
Makefile assumes that Ranch is in its deps folder. If Cowboy
is a part of a bigger application, and most often it will be
in such a role rather than a standalone application, then
all dependencies should be kept in one place. In that case
it would be the main project's deps folder, not Cowboy's
deps folder. Can the compilation process be split into
compiling Cowboy dependencies separately from Cowboy itself?<br>
<br>
something like:<br>
<br>
all: compile-deps compile-cowboy<br>
<br>
Then if Cowboy is a dependency itself it may be just
compiled without the dependency (as it will be compiled when
the main project is compiled).<br>
<br>
_______________________________________________<br>
Extend mailing list<br>
<a moz-do-not-send="true"
href="mailto:Extend@lists.ninenines.eu" target="_blank">Extend@lists.ninenines.eu</a><br>
<a moz-do-not-send="true"
href="http://lists.ninenines.eu:81/listinfo/extend"
target="_blank">http://lists.ninenines.eu:81/listinfo/extend</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>