diff options
Diffstat (limited to 'archives/extend/attachments/20130204/c34e6aa6/attachment.html')
-rw-r--r-- | archives/extend/attachments/20130204/c34e6aa6/attachment.html | 79 |
1 files changed, 79 insertions, 0 deletions
diff --git a/archives/extend/attachments/20130204/c34e6aa6/attachment.html b/archives/extend/attachments/20130204/c34e6aa6/attachment.html new file mode 100644 index 00000000..723b1717 --- /dev/null +++ b/archives/extend/attachments/20130204/c34e6aa6/attachment.html @@ -0,0 +1,79 @@ +<tt> +<html><br> + <head><br> + <meta content="text/html; charset=ISO-8859-1"<br> + http-equiv="Content-Type"><br> + </head><br> + <body text="#000000" bgcolor="#FFFFFF"><br> + <div class="moz-cite-prefix"><br> + <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> + <br><br> + Am I to understand that the only way of having the dependencies in<br> + another folder than cowboy/deps is to use Rebar (e.g. if compiling<br> + using the makefile it will always assume that dependencies are in<br> + local deps folder)?<br><br> + <br><br> + Would be good to have a target to compile cowboy without<br> + dependencies.<br><br> + <br><br> + <br><br> + On 04/02/2013 20:10, Jeremy Ong wrote:<br><br> + </div><br> + <blockquote<br> +cite="mid:CAKD1GY7+fvMOR6PhOz=QGAi8r2T_Obf4gCjaH4hN_=J+hNyw4w@mail.gmail.com"<br> + type="cite"><br> + <div dir="ltr">It is rebar compatible<br> + <div><br><br> + </div><br> + <div><a moz-do-not-send="true"<br> + href="https://github.com/extend/cowboy/blob/master/rebar.config">https://github.com/extend/cowboy/blob/master/rebar.config</a><br><br> + </div><br> + <div><br><br> + </div><br> + <div style=""><br> + I use it with rebar all the time.</div><br> + </div><br> + <div class="gmail_extra"><br><br> + <br><br> + <div class="gmail_quote">On Thu, Jan 24, 2013 at 2:41 PM,<br> + Grzegorz Junka <span dir="ltr"><<a moz-do-not-send="true"<br> + href="mailto:[email protected]" target="_blank">[email protected]</a>></span><br> + wrote:<br><br> + <blockquote class="gmail_quote" style="margin:0 0 0<br> + .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br><br> + I understand the move away from Rebar but I'd like to see<br> + the project to be still Rebar-compatible. Would that be a<br> + problem? Mainly I am thinking about dependencies. The Cowboy<br> + Makefile assumes that Ranch is in its deps folder. If Cowboy<br> + is a part of a bigger application, and most often it will be<br> + in such a role rather than a standalone application, then<br> + all dependencies should be kept in one place. In that case<br> + it would be the main project's deps folder, not Cowboy's<br> + deps folder. Can the compilation process be split into<br> + compiling Cowboy dependencies separately from Cowboy itself?<br><br> + <br><br> + something like:<br><br> + <br><br> + all: compile-deps compile-cowboy<br><br> + <br><br> + Then if Cowboy is a dependency itself it may be just<br> + compiled without the dependency (as it will be compiled when<br> + the main project is compiled).<br><br> + <br><br> + _______________________________________________<br><br> + Extend mailing list<br><br> + <a moz-do-not-send="true"<br> + href="mailto:[email protected]" target="_blank">[email protected]</a><br><br> + <a moz-do-not-send="true"<br> + href="http://lists.ninenines.eu:81/listinfo/extend"<br> + target="_blank">http://lists.ninenines.eu:81/listinfo/extend</a><br><br> + </blockquote><br> + </div><br> + <br><br> + </div><br> + </blockquote><br> + <br><br> + </body><br> +</html><br> + +</tt> |