1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<HEAD>
<TITLE> [99s-extend] [erlang-questions] [ANN] erlang.mk build tool
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20%5Berlang-questions%5D%20%5BANN%5D%20erlang.mk%20build%20tool&In-Reply-To=%3C520E3A5F.7000800%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="000214.html">
<LINK REL="Next" HREF="000218.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[99s-extend] [erlang-questions] [ANN] erlang.mk build tool</H1>
<B>Loïc Hoguin</B>
<A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20%5Berlang-questions%5D%20%5BANN%5D%20erlang.mk%20build%20tool&In-Reply-To=%3C520E3A5F.7000800%40ninenines.eu%3E"
TITLE="[99s-extend] [erlang-questions] [ANN] erlang.mk build tool">essen at ninenines.eu
</A><BR>
<I>Fri Aug 16 16:42:39 CEST 2013</I>
<P><UL>
<LI>Previous message: <A HREF="000214.html">[99s-extend] [erlang-questions] [ANN] erlang.mk build tool
</A></li>
<LI>Next message: <A HREF="000218.html">[99s-extend] [erlang-questions] [ANN] erlang.mk build tool
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#216">[ date ]</a>
<a href="thread.html#216">[ thread ]</a>
<a href="subject.html#216">[ subject ]</a>
<a href="author.html#216">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Well I'm sure if you create a base Makefile (without erlang.mk) that
exports DEPS_DIR and then call $(MAKE) on all folders in /apps (which
would themselves contain Makefiles that use erlang.mk), it would work
just fine. You can still keep only one erlang.mk in your repos and use
include ../../erlang.mk instead for example.
But know that this folder structure is a rebar thing and not standard
(just like /deps you'll say, but that one is insanely useful regardless
of the project structure otherwise).
On 08/16/2013 02:27 PM, Steve Strong wrote:
><i> Looks good - I like simple! Quick question, does it support multiple
</I>><i> applications, for example a project laid out as:
</I>><i>
</I>><i> /proj
</I>><i> /deps
</I>><i> /stuff
</I>><i>
</I>><i> /apps
</I>><i> /app1
</I>><i> /app2
</I>><i>
</I>><i> Most of our stuff is in that form, with shared dependencies between the
</I>><i> various apps. Rebar is quite happy with that format, but I can't see
</I>><i> how to persuade erlang.mk to handle that.
</I>><i>
</I>><i> Cheers,
</I>><i>
</I>><i> Steve
</I>><i>
</I>><i> --
</I>><i> Steve Strong
</I>><i> Sent with Sparrow <<A HREF="http://www.sparrowmailapp.com/?sig">http://www.sparrowmailapp.com/?sig</A>>
</I>><i>
</I>><i> On Thursday, 15 August 2013 at 16:19, Loïc Hoguin wrote:
</I>><i>
</I>>><i> Hello friendly people,
</I>>><i>
</I>>><i> I would like to make an official announcement of erlang.mk now that all
</I>>><i> the features I wanted are in.
</I>>><i>
</I>>><i> erlang.mk is a rebar replacement. It was initially created for allowing
</I>>><i> a faster development process than rebar and for better compatibility
</I>>><i> with Linux build tools. It should work on Linux and OSX with GNU Make
</I>>><i> installed.
</I>>><i>
</I>>><i> Projects using erlang.mk are still compatible with rebar. Dependencies
</I>>><i> fetched by rebar are stored in the same deps/ directory, and projects
</I>>><i> using erlang.mk can still be used as rebar dependencies, with or without
</I>>><i> a rebar.config file.
</I>>><i>
</I>>><i> erlang.mk also features a simple package index. Try `make pkg-list` to
</I>>><i> list all packages currently available. All the packages listed are
</I>>><i> compatible with erlang.mk with no tweaking required.
</I>>><i>
</I>>><i> Makefiles written with erlang.mk are *VERY* simple, here are two examples:
</I>>><i>
</I>>><i> * <A HREF="https://github.com/extend/farwest/blob/master/Makefile">https://github.com/extend/farwest/blob/master/Makefile</A>
</I>>><i> * <A HREF="https://github.com/extend/cowboy/blob/master/Makefile">https://github.com/extend/cowboy/blob/master/Makefile</A>
</I>>><i>
</I>>><i> I wrote about erlang.mk and relx recently on the Nine Nines blog.
</I>>><i> erlang.mk is the perfect companion to relx.
</I>>><i>
</I>>><i> * <A HREF="http://ninenines.eu/articles/erlang.mk-and-relx">http://ninenines.eu/articles/erlang.mk-and-relx</A>
</I>>><i>
</I>>><i> Here are examples of projects that are using and compatible with
</I>>><i> erlang.mk:
</I>>><i>
</I>>><i> * <A HREF="https://github.com/jlouis/etorrent">https://github.com/jlouis/etorrent</A>
</I>>><i> * <A HREF="https://github.com/extend/cowboy">https://github.com/extend/cowboy</A>
</I>>><i> * <A HREF="https://github.com/extend/farwest">https://github.com/extend/farwest</A>
</I>>><i>
</I>>><i> You can find erlang.mk at the following URL:
</I>>><i>
</I>>><i> * <A HREF="https://github.com/extend/erlang.mk">https://github.com/extend/erlang.mk</A>
</I>>><i>
</I>>><i> Contributions to the package index are of course welcome! The only
</I>>><i> requirement is that the package is to be compatible with erlang.mk
</I>>><i> itself. Just send a PR to the erlang.mk project updating the
</I>>><i> packages.v1.txt!
</I>>><i>
</I>>><i> Enjoy!
</I>>><i>
</I>>><i> --
</I>>><i> Loïc Hoguin
</I>>><i> Erlang Cowboy
</I>>><i> Nine Nines
</I>>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A>
</I>>><i> _______________________________________________
</I>>><i> erlang-questions mailing list
</I>>><i> <A HREF="https://lists.ninenines.eu/listinfo/extend">erlang-questions at erlang.org</A> <mailto:<A HREF="https://lists.ninenines.eu/listinfo/extend">erlang-questions at erlang.org</A>>
</I>>><i> <A HREF="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</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="000214.html">[99s-extend] [erlang-questions] [ANN] erlang.mk build tool
</A></li>
<LI>Next message: <A HREF="000218.html">[99s-extend] [erlang-questions] [ANN] erlang.mk build tool
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#216">[ date ]</a>
<a href="thread.html#216">[ thread ]</a>
<a href="subject.html#216">[ subject ]</a>
<a href="author.html#216">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend
mailing list</a><br>
</body></html>
|
