19 Mar
2019
19 Mar
'19
8:10 p.m.
On Tue 19 Mar 2019 at 03:43 +0100, Jikstra wrote:
One thing to keep in mind about system-installed
deltachat or deltachat-node is that we need to be able
to link deltachat-node against a specific core version.
libdeltachat should export it's version in it's .h file so that a
consumer of it can fail to build if it's too old.
For the meson things and android:
I like splitting netpgp... into own repositories. Pulling them in
is quite easy with mesons built in wrapdb. We could even add
it to https://wrapdb.mesonbuild.com/ so other people can also
easily pull those dependencies in.
Yes, we an move netpgp into it's own repository and even go the full
wrapdb way. It's a nice to have but not high on the priority to unblock
things. But if someone wants to work on this I'll be happy to give
pointers where I can.
So tl;dr: I'm fine with -node pointing to a system
installed
libdeltachat by default but i think it makes sense to also have
a fallback variant to get it from github & compile it to make
it easier to switch between branches which use different -node
or -core versions.
Sure, when I first created the issue on github to compile dc-node
against system dc-core I was worried about this workflow for dc-node
devs but was told it's not a high priority. But if it is, like you
argue here, let's work out a way to support it.