[jitsi-dev] document (or manage) native dependencies


#1

I've filled this issue already as JITSI-995 without knowing your procedures.
Please reopen this issue if you want to solve it.

There's no central location where one can see which C libraries of what
version, origin and license Jitsi uses, which of them are patched, in what way
and for what reason.

I'm not a C developer so I don't know if there's something like Maven/Ivy for
C that manages dependencies?

Thomas Koch, http://www.koch.ro


#2

Hey

There's no central location where one can see which C libraries of what
version, origin and license Jitsi uses, which of them are patched, in
what way and for what reason.

How do other (Debian) packaged applications deal with such stuff?

I'm not a C developer so I don't know if there's something like Maven/Ivy for
C that manages dependencies?

I don't know of anything, which is probably because it doesn't make much sense for native code. You would have to deal with too many variations of compilers, architectures and operating systems.

Ingo


#3

Bauersachs Ingo:

Hey

> There's no central location where one can see which C libraries of what
> version, origin and license Jitsi uses, which of them are patched, in
> what way and for what reason.

How do other (Debian) packaged applications deal with such stuff?

> I'm not a C developer so I don't know if there's something like Maven/Ivy
> for C that manages dependencies?

I don't know of anything, which is probably because it doesn't make much
sense for native code. You would have to deal with too many variations of
compilers, architectures and operating systems.

I've asked on debian-devel[1] and they suggest:

- use pkg-config[2]
- provide a plain text file to document the C dependencies

[1] http://lists.debian.org/debian-devel/2011/11/msg00692.html
[2] http://en.wikipedia.org/wiki/Pkg-config

Regards,

Thomas Koch, http://www.koch.ro