ck" however, the build of ysrc.c
> can't find x.h, and terminates.
>
> The suggestion I've seen for dependent libraries is to make libx be a
> SUBDIR of liby. I could do this, but it brings up two questions:
>
> (a) Will bin1/, bin1/tests/, and bin2/ be able to find
ory off of
$includedir. During "make", gcc for ysrc.c gets -I../libx, so the
build is fine. During "make distcheck" however, the build of ysrc.c
can't find x.h, and terminates.
The suggestion I've seen for dependent libraries is to make libx be a
SUBDIR of liby. I could do t
Hello,
On Wed, Jan 12, 2005 at 02:25:03PM +0100, Giovanni Bricconi wrote:
> 1. make install installs the library and the sample module, but does
> not install the headers
...
> the Makefile.am in includes directory, does not work, if I call make
> install from includes headers get installe
I'm new to automake and autoconf, I'm now trying to write my first
project using these tools.
My project consists in a library and a sample apache module that depends
on this library.
The directory structure I have chosen is the following:
my_project (contains configure.ac and top Makefile
>>> "Bj|rn" == Bj|rn Englund <[EMAIL PROTECTED]> writes:
Bj|rn> Is there any hope of getting this problem solved any time soon?
Bj|rn> (PR 376 at http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=automake)
Bj|rn> Is someone working on it?
I don't think so, but that would be welcome...
h
Is there any hope of getting this problem solved any time soon?
(PR 376 at http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=automake)
Is someone working on it?
Is there a workaround other than putting the libraries in
the same install directory?
In my case I can solve this manually by doi
Hello automake,
I've run into couple of problems while trying to build mutually
dependent libraries (i.e. ones which import symbols from one another).
It first seemed to me that automake simply do not have support for
them. However, I was able to solve them in quite acceptable for m
