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
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
Hello Adam,
* Adam Mercer wrote on Fri, Jun 26, 2009 at 09:23:03PM CEST:
> make: Circular CudaChisq.cu <- CudaChisq.cu.c dependency dropped.
>
> The following rule is used to generate the .c file from the .cu source:
>
> CudaChisq.cu.c: CudaChisq.cu
> nvcc -cuda --host-compilation=c $(INCL
Hi
I'm in the middle of integrating some CUDA code, for utilising GPUs,
into one of our projects and seeing the following warning returned
from make:
make: Circular CudaChisq.cu <- CudaChisq.cu.c dependency dropped.
The following rule is used to generate the .c file from the .cu source:
CudaChi
