Re: Build rules for CUDA source files

2010-09-10 Thread Adam Mercer
On Thu, Sep 9, 2010 at 15:55, Ralf Wildenhues wrote: > Showing the line before this would have been interesting. I'm doing all this testing on Debian Lenny, which has libtool-1.5.29. I don't really want to upgrade libtool unless I really have to. > Yes.  You add -Xcompiler -fPIC to compile flag

Re: Build rules for CUDA source files

2010-09-09 Thread Ralf Wildenhues
* Adam Mercer wrote on Thu, Sep 09, 2010 at 10:42:31PM CEST: > On Thu, Sep 9, 2010 at 15:27, Ralf Wildenhues wrote: > > For libtool libraries, it will try for a CudaFFT.lo file. > > of course. > > > You may be > > able to create a .cu.lo rule to generate that.  I think.  Since I'm not > > sure th

Re: Build rules for CUDA source files

2010-09-09 Thread Adam Mercer
On Thu, Sep 9, 2010 at 15:27, Ralf Wildenhues wrote: Ralf >> pkginclude_HEADERS = \ >>   ComplexFFT.h \ >>   RealFFT.h \ >>   FFTWMutex.h \ >>   TimeFreqFFT.h \ >>   CudaPlan.h > > JFTR, headers not going to be installed can be listed in *_SOURCES as > well. I know, we need all the headers inst

Re: Build rules for CUDA source files

2010-09-09 Thread Ralf Wildenhues
* Adam Mercer wrote on Thu, Sep 09, 2010 at 10:17:03PM CEST: > I'm working on adding some code that uses the NVidia CUDA compiler and > libraries to one of our projects. I believe that I have added the > appropriate rules to Makefile.am to specify how to do the build: > > noinst_LTLIBRARIES = libf

Build rules for CUDA source files

2010-09-09 Thread Adam Mercer
Hi I'm working on adding some code that uses the NVidia CUDA compiler and libraries to one of our projects. I believe that I have added the appropriate rules to Makefile.am to specify how to do the build: noinst_LTLIBRARIES = libfft.la libfft_la_SOURCES = \ TimeFreqFFT.c \ AverageSpectrum.c \