[99s-extend] Cowboy Makefile

[Grzegorz Junka]

deps/ranch:
@mkdir -p $(DEPS_DIR)
git clone -n -- https://github.com/extend/ranch.git $(DEPS_DIR)/ranch
cd $(DEPS_DIR)/ranch ; git checkout -q $(RANCH_VSN)


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)?

Would be good to have a target to compile cowboy without dependencies.


On 04/02/2013 20:10, Jeremy Ong wrote:
> It is rebar compatible
>
> https://github.com/extend/cowboy/blob/master/rebar.config
>
> I use it with rebar all the time.
>
>
> On Thu, Jan 24, 2013 at 2:41 PM, Grzegorz Junka <list1 at gjunka.com 
> <mailto:list1 at gjunka.com>> wrote:
>
>     Hi,
>     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?
>
>     something like:
>
>     all: compile-deps compile-cowboy
>
>     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).
>
>     _______________________________________________
>     Extend mailing list
>     Extend at lists.ninenines.eu <mailto:Extend at lists.ninenines.eu>
>     http://lists.ninenines.eu:81/listinfo/extend
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ninenines.eu/archives/extend/attachments/20130204/c34e6aa6/attachment.html>