With the introduction of Elixir 1.8, Mix.target() was added. This had the side effect of breaking packages that build C code that is not built by an updated version of elixir_make including this project's dependency on esqlite. esqlite is built by pc (port compiler, a rebar3 plugin). I believe it is unreasonable to ask Rebar to support the Elixir Mix.target(), but any thing that needs to be cross compiled is now broken.
I've drafted up one solution that i am incredibly unhappy with.
1) add {:elixir_make, "~> 0.5", runtime: false} to the deps
2) add a Makefile that basically recompiles the same assets that pc has already emitted:
This has 1 positive side effect of allowing us to control the compiler options to sqlite independently of esqlite. This may or may not be a good thing.
With the introduction of Elixir 1.8,
Mix.target()
was added. This had the side effect of breaking packages that build C code that is not built by an updated version ofelixir_make
including this project's dependency onesqlite
.esqlite
is built bypc
(port compiler, a rebar3 plugin). I believe it is unreasonable to ask Rebar to support the ElixirMix.target()
, but any thing that needs to be cross compiled is now broken.I've drafted up one solution that i am incredibly unhappy with.
1) add
{:elixir_make, "~> 0.5", runtime: false}
to the deps 2) add aMakefile
that basically recompiles the same assets thatpc
has already emitted:This has 1 positive side effect of allowing us to control the compiler options to sqlite independently of
esqlite
. This may or may not be a good thing.There is another potential solution in #53 on esqlite