<div dir="ltr">Yes sorry, I was saying create an application for the single module<br><br><font size="1"><span style="font-family: courier new,monospace;">/myrel</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;"> |- lib/</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;"> |- singlemodule-1.0/</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;"> |- src/</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;"> |- mymodule.erl</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;"> |- ebin/</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;"> |- singlemodule.app </span><span style="font-family: courier new,monospace;"></span><span style="font-family: courier new,monospace;"></span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">
|- app2/...</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;"> |- app3/...</span></font><br><br>with singlemodule.app looking like<br><br><font size="1"><span style="font-family: courier new,monospace;">{application, singlemodule, [</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;"> {description, "Description"},</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;"> {vsn, "1.0"},</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;"> {modules,[mymodule]},</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;"> {registered,[]},</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;"> {applications, [kernel, stdlib]}</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">]}.</span></font><br><br>You dont need supervisors / servers to start and stop etc, it just makes<br>
sure theres no name conflicts and that its in the path<br><br><div class="gmail_quote">2008/8/30 Mazen Harake <span dir="ltr"><<a href="mailto:mazen@erlang-consulting.com">mazen@erlang-consulting.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">You should do as you already suggested... make a library application. It<br>
is not overkill, it is good practice. If you add it to your rel-file and<br>
use OTP release handling with that then the library will always be part<br>
of your release. This is a good thing<br>
/Mazen<br>
<div class="Ih2E3d"><br>
Matt Williamson wrote:<br>
> To make things clear. My goal is to share a library module across<br>
> multiple application in a release, but I'm not quite sure how to go<br>
> about it.<br>
><br>
> On Sat, Aug 30, 2008 at 8:22 AM, Dale Harvey <<a href="mailto:harveyd@gmail.com">harveyd@gmail.com</a><br>
</div><div class="Ih2E3d">> <mailto:<a href="mailto:harveyd@gmail.com">harveyd@gmail.com</a>>> wrote:<br>
><br>
> you only need to write a .app file<br>
> from <a href="http://erlang.org/doc/design_principles/applications.html#7" target="_blank">http://erlang.org/doc/design_principles/applications.html#7</a><br>
><br>
> The contents of a minimal .app file for a library application<br>
> libapp looks like this:<br>
><br>
> {application, libapp, []}.<br>
><br>
><br>
> (I think the docs might be misleading though, I got errors using<br>
> the minimal,<br>
> this is what I use<br>
><br>
> {application, appname, [<br>
> {description, "Description"},<br>
> {vsn, "1.0"},<br>
> {modules,[]},<br>
> {registered,[]},<br>
> {applications, [kernel, stdlib]}<br>
> ]}.<br>
><br>
> then have systools find that app file when generating the .rel<br>
><br>
> 2008/8/30 Matt Williamson <<a href="mailto:dawsdesign@gmail.com">dawsdesign@gmail.com</a><br>
</div>> <mailto:<a href="mailto:dawsdesign@gmail.com">dawsdesign@gmail.com</a>>><br>
<div class="Ih2E3d">><br>
> Let's say I have a typical release directory like so:<br>
><br>
> /myrel<br>
> |- lib/<br>
> |- app1/<br>
> |- src/<br>
> |- ebin/<br>
> |- include/<br>
> |- doc/<br>
> |- app2/...<br>
> |- app3/...<br>
><br>
> How would I include a single module, which can be called by<br>
> modules in all of the applications? The only two ways I can<br>
> think of is make it into an app (I personally think that's<br>
> overkill because I just want to call a function in the module)<br>
> or make a symlink, which won't work in windows.<br>
><br>
> _______________________________________________<br>
> erlang-questions mailing list<br>
</div>> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a> <mailto:<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>><br>
<div class="Ih2E3d">> <a href="http://www.erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://www.erlang.org/mailman/listinfo/erlang-questions</a><br>
><br>
><br>
><br>
</div>> ------------------------------------------------------------------------<br>
<div class="Ih2E3d">><br>
> _______________________________________________<br>
> erlang-questions mailing list<br>
> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
> <a href="http://www.erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://www.erlang.org/mailman/listinfo/erlang-questions</a><br>
<br>
<br>
</div>--<br>
Mazen Harake <<a href="mailto:mazen@erlang-consulting.com">mazen@erlang-consulting.com</a>><br>
Erlang Software Developer and Consultant,<br>
Erlang Training & Consulting, Ltd<br>
<br>
Mobile Phone: +44 (0)795 13 26 317<br>
Office Phone: +44 (0)207 45 61 020<br>
Office Address:<br>
401 London Fruit & Wool Exchange<br>
Brushfield St, London, E1 6EL<br>
United Kingdom<br>
<br>
This email and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of "Erlang Training & Consulting, Ltd".<br>
<br>
If you are not the intended recipient of this email and its attachments, you must take no action based upon them, nor must you copy or show them to anyone. Please contact the sender if you believe you have received this email in error.<br>
<div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<a href="http://www.erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://www.erlang.org/mailman/listinfo/erlang-questions</a><br>
</div></div></blockquote></div><br></div>