blob: 4e04e9305979a53fc2db0e708531de78768a9f45 (
plain) (
tree)
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<HEAD>
<TITLE> [99s-extend] Cowboy Makefile
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Cowboy%20Makefile&In-Reply-To=%3C51102F0F.6060607%40ninenines.eu%3E">
<META NAME="robots" CONTENT="index,nofollow">
<style type="text/css">
pre {
white-space: pre-wrap; /* css-2.1, curent FF, Opera, Safari */
}
</style>
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000044.html">
<LINK REL="Next" HREF="000046.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[99s-extend] Cowboy Makefile</H1>
<B>Loïc Hoguin</B>
<A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Cowboy%20Makefile&In-Reply-To=%3C51102F0F.6060607%40ninenines.eu%3E"
TITLE="[99s-extend] Cowboy Makefile">essen at ninenines.eu
</A><BR>
<I>Mon Feb 4 22:58:39 CET 2013</I>
<P><UL>
<LI>Previous message: <A HREF="000044.html">[99s-extend] Cowboy Makefile
</A></li>
<LI>Next message: <A HREF="000046.html">[99s-extend] Big body via REST
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#45">[ date ]</a>
<a href="thread.html#45">[ thread ]</a>
<a href="subject.html#45">[ subject ]</a>
<a href="author.html#45">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Cowboy is still compatible with rebar like before, there's no change you
need to do.
If however you would like to compile using the Makefile regardless,
there's a small thing that needs to be fixed before it's good.
On 02/04/2013 10:50 PM, Grzegorz Junka wrote:
><i> deps/ranch:
</I>><i> @mkdir -p $(DEPS_DIR)
</I>><i> git clone -n -- <A HREF="https://github.com/extend/ranch.git">https://github.com/extend/ranch.git</A> $(DEPS_DIR)/ranch
</I>><i> cd $(DEPS_DIR)/ranch ; git checkout -q $(RANCH_VSN)
</I>><i>
</I>><i>
</I>><i> Am I to understand that the only way of having the dependencies in
</I>><i> another folder than cowboy/deps is to use Rebar (e.g. if compiling using
</I>><i> the makefile it will always assume that dependencies are in local deps
</I>><i> folder)?
</I>><i>
</I>><i> Would be good to have a target to compile cowboy without dependencies.
</I>><i>
</I>><i>
</I>><i> On 04/02/2013 20:10, Jeremy Ong wrote:
</I>>><i> It is rebar compatible
</I>>><i>
</I>>><i> <A HREF="https://github.com/extend/cowboy/blob/master/rebar.config">https://github.com/extend/cowboy/blob/master/rebar.config</A>
</I>>><i>
</I>>><i> I use it with rebar all the time.
</I>>><i>
</I>>><i>
</I>>><i> On Thu, Jan 24, 2013 at 2:41 PM, Grzegorz Junka <<A HREF="https://lists.ninenines.eu/listinfo/extend">list1 at gjunka.com</A>
</I>>><i> <mailto:<A HREF="https://lists.ninenines.eu/listinfo/extend">list1 at gjunka.com</A>>> wrote:
</I>>><i>
</I>>><i> Hi,
</I>>><i> I understand the move away from Rebar but I'd like to see the
</I>>><i> project to be still Rebar-compatible. Would that be a problem?
</I>>><i> Mainly I am thinking about dependencies. The Cowboy Makefile
</I>>><i> assumes that Ranch is in its deps folder. If Cowboy is a part of a
</I>>><i> bigger application, and most often it will be in such a role
</I>>><i> rather than a standalone application, then all dependencies should
</I>>><i> be kept in one place. In that case it would be the main project's
</I>>><i> deps folder, not Cowboy's deps folder. Can the compilation process
</I>>><i> be split into compiling Cowboy dependencies separately from Cowboy
</I>>><i> itself?
</I>>><i>
</I>>><i> something like:
</I>>><i>
</I>>><i> all: compile-deps compile-cowboy
</I>>><i>
</I>>><i> Then if Cowboy is a dependency itself it may be just compiled
</I>>><i> without the dependency (as it will be compiled when the main
</I>>><i> project is compiled).
</I>>><i>
</I>>><i> _______________________________________________
</I>>><i> Extend mailing list
</I>>><i> <A HREF="https://lists.ninenines.eu/listinfo/extend">Extend at lists.ninenines.eu</A> <mailto:<A HREF="https://lists.ninenines.eu/listinfo/extend">Extend at lists.ninenines.eu</A>>
</I>>><i> <A HREF="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A>
</I>>><i>
</I>>><i>
</I>><i>
</I>><i>
</I>><i>
</I>><i> _______________________________________________
</I>><i> Extend mailing list
</I>><i> <A HREF="https://lists.ninenines.eu/listinfo/extend">Extend at lists.ninenines.eu</A>
</I>><i> <A HREF="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A>
</I>><i>
</I>
--
Loïc Hoguin
Erlang Cowboy
Nine Nines
<A HREF="http://ninenines.eu">http://ninenines.eu</A>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000044.html">[99s-extend] Cowboy Makefile
</A></li>
<LI>Next message: <A HREF="000046.html">[99s-extend] Big body via REST
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#45">[ date ]</a>
<a href="thread.html#45">[ thread ]</a>
<a href="subject.html#45">[ subject ]</a>
<a href="author.html#45">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend
mailing list</a><br>
</body></html>
|
