Thanks Tom! Works like a charm...
Tom Tromey wrote:
> Dave> Thanks everyone. Right now I'm just using the as a workaround
> Dave> until the automake problem is fixed. I'm only worried about GNU
> Dave> make on Cywin at the moment.
>
> I recently checked in a bug fix which fixes the test case.
>
Dave> Thanks everyone. Right now I'm just using the as a workaround
Dave> until the automake problem is fixed. I'm only worried about GNU
Dave> make on Cywin at the moment.
I recently checked in a bug fix which fixes the test case.
Could you try the cvs automake to see if it works for you?
Tom
Thanks everyone. Right now I'm just using the as a workaround until the
automake problem is fixed. I'm only worried about GNU make on Cywin at
the moment.
Dave
Lars J. Aas wrote:
> On Mon, Jan 15, 2001 at 06:37:38PM +0100, Akim Demaille wrote:
> : Hm, it looks like it's removed only in the to
On Mon, Jan 15, 2001 at 06:37:38PM +0100, Akim Demaille wrote:
: Hm, it looks like it's removed only in the top dir. It also seems
: you've been saved by the colon :) But apparently, expect problems
: with Sun? Dunno.
If I recall correctly, IRIX make supports $VPATH in the sense that
it will u
> "Dave" == Dave Brolley <[EMAIL PROTECTED]> writes:
Dave> No problems so far. What kind of problems are you expecting?
It likes removing VPATH definitions from Makefiles. Many people
complain about that, but I confess I never really tried to understand
what the problem was. I just know th
> "Dave" == Dave Brolley <[EMAIL PROTECTED]> writes:
Dave> FWIW, I'm working around this for now using VPATH:
Dave>VPATH=$(srcdir):../host
Dave> and specifying h1.cpp without a path in in
Dave> libfred_la_SOURCES. Seems to work OK. Is this supported?
I'm afraid not. I believe some versi
Akim Demaille wrote:
>> "Dave" == Dave Brolley <[EMAIL PROTECTED]> writes:
>
>
> Dave> FWIW, I'm working around this for now using VPATH:
>
> Dave>VPATH=$(srcdir):../host
>
> Dave> and specifying h1.cpp without a path in in
> Dave> libfred_la_SOURCES. Seems to work OK. Is this sup
> "Dave" == Dave Brolley <[EMAIL PROTECTED]> writes:
Dave> FWIW, I'm working around this for now using VPATH:
Dave>VPATH=$(srcdir):../host
Dave> and specifying h1.cpp without a path in in
Dave> libfred_la_SOURCES. Seems to work OK. Is this supported?
Expect problems with Autoconf...
Tom Tromey wrote:
>> "Dave" == Dave Brolley <[EMAIL PROTECTED]> writes:
>
>
> Dave> To work around the problem I have to change the generated dependency to:
>
> Dave>h1.lo: ../host/h1.cpp
> Dave>$(LTCXXCOMPILE) -c -o $@ $<
>
> Dave> Is this a make bug, or should automake
> "Dave" == Dave Brolley <[EMAIL PROTECTED]> writes:
Dave> To work around the problem I have to change the generated dependency to:
Dave>h1.lo: ../host/h1.cpp
Dave>$(LTCXXCOMPILE) -c -o $@ $<
Dave> Is this a make bug, or should automake be generating a rule for
Dave> making hl.l
Hi,
One of the reasons I tried automake 1.4b was to see if the support for
compiling sources from other directories had been included. I was
delighted to see that some work has been done in this area. Using my
previous example, the directory structure is something like:
src/main -- most of th
On Dec 15, 2000, Dave Brolley <[EMAIL PROTECTED]> wrote:
> The problem is that h1.o is in the 'main' subdirectory along with all of the
> other object files. What's the right way to build a few sources from another
> directory into an application?
Which version of automake are you using? Buildi
Hi,
I want ot use automake to build a library for which the source has been
supplied to me by a customer. The directory structure is something like:
src/main -- most of the source files are here
src/host -- a few host-specific source files here
In src/main, I have a Makefile.am containing some
13 matches
Mail list logo
