* mhoenicka wrote on Sun, Sep 26, 2010 at 11:49:38PM CEST:
> Ralf Wildenhues wrote:
> >
> > Having .pc files installed with install-exec can be done with something
> > like
> >
> > pkgconfigexecdir = $(libdir)/pkg-config
> > pkgconfigexec_DATA = foo.pc
>
> That works like a charm. Now all I have
Ralf Wildenhues wrote:
>
>
> Having .pc files installed with install-exec can be done with something
> like
>
> pkgconfigexecdir = $(libdir)/pkg-config
> pkgconfigexec_DATA = foo.pc
>
>
That works like a charm. Now all I have to take care of are the include
files of the library, which by de
* mhoenicka wrote on Sun, Sep 26, 2010 at 09:53:11PM CEST:
> Thanks for your hints. In fact, the install-exec vs. install-data thing is
> good enough for half of the problem. To keep things simple I didn't mention
> that we're talking about two related projects, one providing a library, the
> other
Ralf Wildenhues wrote:
>
>
> There is also 'install-exec' which only installs platform-dependent
> files, and 'install-data' which does the rest, maybe that is already
> good enough for you? See info Automake "The Two Parts of Install".
>
>
Thanks for your hints. In fact, the install-exec v
Hello Markus,
* mhoenicka wrote on Sat, Sep 25, 2010 at 12:02:19AM CEST:
> I'm maintaining a software project which uses a pretty straightforward
> automake/autoconf/libtool setup to build and install the software and the
> documentation. The documentation is maintainer-built and shipped with the
