From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Thu, 5 Feb 2015 08:55:25 +0100 Subject: [Buildroot] [PATCH v6 16/16] ejabberd: new package. In-Reply-To: References: <1421055140-5092-1-git-send-email-johan.oudinet@gmail.com> <1421055140-5092-17-git-send-email-johan.oudinet@gmail.com> <20150203105629.0abbbe46@free-electrons.com> <20150203123253.13838ada@free-electrons.com> Message-ID: <20150205085525.140473af@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Dear Frank Hunleth, On Wed, 4 Feb 2015 16:17:25 -0500, Frank Hunleth wrote: > I'm not going to claim to be an Erlang expert, but I can add some > information. Applications that use lager need to enable Lager's parse > transform on the host Erlang compiler. The parse transform extracts > things like module, function, and line number information whenever > lager:warn, lager:info, etc. are called, so that it can be included in > the log messages. The parse transform actually has to be compiled for > the host. When you're not cross-compiling, it doesn't look as weird. Ok, thanks for the explanation. > Also, I should say that I've been quietly watching the various Erlang > patches on the mailing list. What I've seen looks pretty good. I do > use Erlang with Buildroot, but I use the Erlang Release tools to > generate the final images. This makes for smaller root filesystems > (Erlang's libraries are huge and largely irrelevant to most apps) and > is more compatible with how Erlang people do things. However, it's > definitely not how I think that things should be done in the Buildroot > project. I think that you guys are doing it right, so if I work a > project that just needs ejabberd or another Erlang app, then I'm going > to switch over to this framework. Thanks for doing this! Is there a way of doing the same as those Erlang Release tools, and make sure only the really used libraries are kept? Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com