Am Freitag, den 10.10.2008, 22:21 +0200 schrieb Matěj Týč:
> Thank you for your reply, Dan
>
> > And where is the problem? E.g.
> >
> > Name: @PACKAGE@
> >
> This does not work. I need a name of the library that libtool produces
> in the end...
For what? The version numbers are not relevant her
Thank you for your reply, Braden,
> > I am particulary searching for a manner how to specify the library
> > name
> > in a smart way since libtool can be very creative when decorating the
> > library name (if you use the -version-number etc. options).
>
> You don't use that information when lin
Thank you for your reply, Dan
> And where is the problem? E.g.
>
> Name: @PACKAGE@
>
This does not work. I need a name of the library that libtool produces
in the end...
> and then process the .pc.in by configure (AC_CONFIG_FILES). If you don't want
> to
> use $PACKAGE, well then use some self
On Oct 10, 2008, at 2:28 PM, Matěj Týč wrote:
Hello friends,
I would like to inquire whether there is someone here that
generates .pc
files in his autotools-powered project (presumably a project
containing
libraries).
The most common way to do it is to process the file with configure/
c
Matěj Týč wrote:
> Hello friends,
> I would like to inquire whether there is someone here that generates .pc
> files in his autotools-powered project (presumably a project containing
> libraries).
> I am particulary searching for a manner how to specify the library name
> in a smart way since libt
Hello friends,
I would like to inquire whether there is someone here that generates .pc
files in his autotools-powered project (presumably a project containing
libraries).
I am particulary searching for a manner how to specify the library name
in a smart way since libtool can be very creative when
