I'm currently testing erlang-native-compiler with Jiffy. There's a Jiffy branch to add rebar3 support. I failed to make the pc thing work for everyone without issue but this new approach seems to work better (because its just rebar2 minus anything not related to the port compiler). I'm going to clean up the Jiffy PR and merge that. Once that's done we should have a pretty good idea if its a viable approach. Assuming that works its a fairly minimal change to update each NIF so that its compilable on both rebar2 and rebar3.
On Mon, Sep 26, 2016 at 3:37 PM, Joan Touzet <[email protected]> wrote: > I'd like to see us move to Rebar 3 as well. Challenges will be compiling > the NIF stuff, especially in a cross-platform stable way. > > GitHub notifications tells me davisp started in on a little thing: > > https://github.com/davisp/erlang-native-compiler > > Perhaps you can make use of this / talk to Paul about it and get things > moving? > > I will sign up to help test on Windows once you've got *nix builds > working correctly. > > -Joan > > ----- Original Message ----- >> From: "Robert Kowalski" <[email protected]> >> To: [email protected] >> Sent: Monday, September 26, 2016 12:31:02 PM >> Subject: Rebar 3 >> >> Hey, >> >> I would like to make it possible to write Elixir for CouchDB >> extensions. >> >> Right now we are using rebar 2 to compile our Erlang and C code. >> There >> is a plugin for rebar to compile Elixir: >> https://github.com/yrashk/rebar_elixir_plugin which is not maintained >> any more. I have compiled Elixir for CouchDB, but it is an aweful >> hack >> as the plugin was written for Elixir 0.9 >> >> This is the main reason why I would like to switch CouchDB to rebar >> 3. >> >> rebar 3 seems to be the way to build / manage Erlang deps right now >> and if nothing speaks against it, I just continue to work on the >> topic. >> >> >> Best, >> Robert >>
