From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Guix-devel <guix-devel@gnu.org>
Subject: Seeking support for implementing Erlang/Rebar3 build system
Date: Sat, 30 May 2020 10:30:10 +0200 [thread overview]
Message-ID: <8f5726d7-8bba-5676-6f4b-db1fcd5d1ef7@crazy-compilers.com> (raw)
Hi,
I started working on a rebar3-build-system for Erlang packages. This a
somewhat crazy idea for me, since I have *not* clue about Erlang and how
it's building and packaging works. (I "just" want to have ejabberd in
guix :-) Based on this, I've already made good progress:
- packaged rebar3 and prepared packages for its dependencies (able to
bootstrap rebar3)
- preliminary rebar3-build-system is done, based on what I've seen at
Debian. (I've not found a build-system for erlang in Nix.)
- basic importer for packages from hex.pm is done
You can find my WIP at
<https://gitlab.digitalcourage.de/htgoebel/guix/-/tree/HG-rebar-build-system>
To get this finished I'm seeking for someone having some experience
about Erlang. My questions are
- How does Erlang find the packages? Do we need to add a
native-search-paths (ERL_LIB?) to the erlang package?
- How to make rebar3 use already build packages and not try for fetch
them from a remote repo? Do we need to copy/link them somewhere, or set
some environment variable?
- Are there standard build targets for rebar3? Currently the
build-system has "compile", "xref" and "doc" - each in a phase of it's
own. Doe this actually make sense?
- Anything else?
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
reply other threads:[~2020-05-30 8:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8f5726d7-8bba-5676-6f4b-db1fcd5d1ef7@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).