Re: busted 'make swig-py'...

Joe Orton <joe@manyfish.co.uk> writes:

> > RUN_SWIG_PY = $(SWIG) -c -python -noproxy $(SWIG_INCLUDES)
> > $(SWIG_PY_INCLUDES) -o $@ $<
> >
> > in my Makefile, so we are telling it how to create the .c for the
> > .i. Furthermore, the command line you sent shows it running the
> > command (except for the $<).
>
> This is a common mistake - you can only use $< in inference rules (.c.o
> style) to be portable. In the BSD make Ben uses $< will expand to
> nothing in this case - in GNU make it will expand to the left-most
> dependency (or all of them, I can't remember).

Interesting. But we use $< in other similar places in Makefile.in.
For example:

# special compilation for files destined for mod_dav_svn
COMPILE_APACHE_MOD = $(LIBTOOL) $(LTFLAGS) --mode=compile \
$(CC) $(CPPFLAGS) $(CFLAGS) $(APACHE_INCLUDES) $(INCLUDES) -o $@ -c $<

And I have no problem building mod_dav_svn at all.... ?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Mar 1 01:10:37 2003