blob: 36cbddbd15961dc89de4af5a01067b9f016cd3f6 (
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=%3CCAKD1GY7%2BfvMOR6PhOz%3DQGAi8r2T_Obf4gCjaH4hN_%3DJ%2BhNyw4w%40mail.gmail.com%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="Next" HREF="000044.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[99s-extend] Cowboy Makefile</H1>
<B>Jeremy Ong</B>
<A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Cowboy%20Makefile&In-Reply-To=%3CCAKD1GY7%2BfvMOR6PhOz%3DQGAi8r2T_Obf4gCjaH4hN_%3DJ%2BhNyw4w%40mail.gmail.com%3E"
TITLE="[99s-extend] Cowboy Makefile">jeremy at quarkgames.com
</A><BR>
<I>Mon Feb 4 21:10:21 CET 2013</I>
<P><UL>
<LI>Next message: <A HREF="000044.html">[99s-extend] Cowboy Makefile
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#43">[ date ]</a>
<a href="thread.html#43">[ thread ]</a>
<a href="subject.html#43">[ subject ]</a>
<a href="author.html#43">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>It is rebar compatible
<A HREF="https://github.com/extend/cowboy/blob/master/rebar.config">https://github.com/extend/cowboy/blob/master/rebar.config</A>
I use it with rebar all the time.
On Thu, Jan 24, 2013 at 2:41 PM, Grzegorz Junka <<A HREF="https://lists.ninenines.eu/listinfo/extend">list1 at gjunka.com</A>> wrote:
><i> Hi,
</I>><i> I understand the move away from Rebar but I'd like to see the project to
</I>><i> be still Rebar-compatible. Would that be a problem? Mainly I am thinking
</I>><i> about dependencies. The Cowboy Makefile assumes that Ranch is in its deps
</I>><i> folder. If Cowboy is a part of a bigger application, and most often it will
</I>><i> be in such a role rather than a standalone application, then all
</I>><i> dependencies should be kept in one place. In that case it would be the main
</I>><i> project's deps folder, not Cowboy's deps folder. Can the compilation
</I>><i> process 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 without the
</I>><i> dependency (as it will be compiled when the main 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>
</I>><i> <A HREF="http://lists.ninenines.eu:81/**listinfo/extend<http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/**listinfo/extend<http://lists.ninenines.eu:81/listinfo/extend</A>>
</I>><i>
</I>-------------- next part --------------
An HTML attachment was scrubbed...
URL: <<A HREF="http://lists.ninenines.eu/archives/extend/attachments/20130204/3c258140/attachment.html">http://lists.ninenines.eu/archives/extend/attachments/20130204/3c258140/attachment.html</A>>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Next message: <A HREF="000044.html">[99s-extend] Cowboy Makefile
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#43">[ date ]</a>
<a href="thread.html#43">[ thread ]</a>
<a href="subject.html#43">[ subject ]</a>
<a href="author.html#43">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend
mailing list</a><br>
</body></html>
|
