Re: add libssh.pc for pkg-config?

[Aris Adamantiadis <aris@xxxxxxxxxxxx>]

Hi Vic,

Imho it can't hurt, but more generaly libssh is easy to link to:
gcc -o program program.c -lssh

*but*

It might become a packaging issue. Let's say that someone wants to have
both libssh0.3.4-dev and libssh0.4-dev: the library files are different
indeed (libssh.so.0.3.4 and libssh.so.0.4.0) but the include files are
in the same directory (/usr/include/libssh/).
Then it may make sense of giving out a script that can point to the good
include directory (/usr/include/libssh0.4) when needed. That directory
would have a symbolic link "libssh" to itself so people can continue
including "libssh/libssh.h" as usual.

I really think it's a package problem and thus something to provide with
packages. Anyone have taken a look at the debian package system yet ?

Aris
Vic Lee a écrit :
> Hi,
> 
> Does it make sense to add a libssh.pc file to support pkg-config in 0.4?
> 
> I think it's quite common to use pkg-config for library development
> nowadays. Please refer to:
> 
> http://en.wikipedia.org/wiki/Pkg-config
> 
> This makes it much easier for projects checking for libssh, and it also
> has native macro PKG_CHECK_MODULES for GNU make systems. And it does not
> affect any other source codes - just an extra file install
> in /usr/lib/pkgconfig.
> 
> Any comments?
> 
> Thanks,
> 
> Vic
> 
> 
>