On Mon, Jun 29, 2009 at 20:29, Ralf Wildenhues wrote:
> Using $< in inference rules, as in my example, is portable.
> In target rules, you can spell out the input file name
> (including an eventual vpath prefix).
Thanks for the clarification.
Cheers
Adam
* Adam Mercer wrote on Mon, Jun 29, 2009 at 10:19:59PM CEST:
> On Sat, Jun 27, 2009 at 05:33, Ralf Wildenhues wrote:
>
> > (Note also that using $< in target rules is not portable to non-GNU
> > make).
>
> Is there a more portable version?
Using $< in inference rules, as in my example, is portab
John,
On 6/29/2009 2:00 PM, johnwohlb...@gmail.com wrote:
On Jun 29, 2009 1:44pm, Ralf Wildenhues wrote:
Hello John, Thanks Ralf. I feel pretty dumb. You know I suspected
that was the problem, and was trying to cd ../. But now I realize I
was putting the cd ../ in the wrong place. After my wr
On Sat, Jun 27, 2009 at 05:33, Ralf Wildenhues wrote:
Ralf
> Why not name the product file CudaChisq.c rather than CudaChisq.cu.c?
> The problem here is that the other half of the circle comes from the
> make-internal rule `%: %.c' for compiling single-source programs.
> I guess you can also avoi
Hi John,
On 6/29/2009 1:44 PM, Ralf Wildenhues wrote:
Hello John,
* johnwohlb...@gmail.com wrote on Mon, Jun 29, 2009 at 09:36:09PM CEST:
in top/lib/Makefile.am
SUBDIRS = pika_comm pika_utilities
# provide a separate recursive target for making tests
tests : all
echo `pwd`;
for dir in $(SU
On Jun 29, 2009 1:44pm, Ralf Wildenhues wrote:
Hello John,
* johnwohlb...@gmail.com wrote on Mon, Jun 29, 2009 at 09:36:09PM CEST:
> in top/lib/Makefile.am
> SUBDIRS = pika_comm pika_utilities
> # provide a separate recursive target for making tests
> tests : all
> echo `pwd`;
> for dir in $(SUB
Hello John,
* johnwohlb...@gmail.com wrote on Mon, Jun 29, 2009 at 09:36:09PM CEST:
> in top/lib/Makefile.am
> SUBDIRS = pika_comm pika_utilities
> # provide a separate recursive target for making tests
> tests : all
> echo `pwd`;
> for dir in $(SUBDIRS); do \
> cd $$dir && $(MAKE) $(AM_MAKEFLAGS)
I need separate targets to build tests and to execute tests, so check-local
alone is not enough. Our machines allow compiling on the "frontend" and
running on the "backend," so I'd like a recursive make target
called "tests" that only compiles the tests, then I'll use check-local for
test e
