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 \

Re: AM_SILENT_RULES doesn't use AS_HELP_STRING?

2010-09-09 Thread Stefano Lattarini
Hi Jeff. Thanks for the report. On Thursday 09 September 2010, Jeff wrote: > I feel a bit silly pointing out something so trivial, Well, I feel a bit sloppy not to having noticed it myself ;-) > but while looking at my configure --help output, I notice that > the help messages generated for AM_S

AM_SILENT_RULES doesn't use AS_HELP_STRING?

2010-09-09 Thread Daily, Jeff A
I feel a bit silly pointing out something so trivial, but while looking at my configure --help output, I notice that the help messages generated for AM_SILENT_RULES are the only ones not aligned with the rest. Any reason this can't be fixed? Thanks. Jeff

Re: How to specify compiler?

2010-09-09 Thread Stefano Lattarini
On Thursday 09 September 2010, Lyre wrote: > Never mind. > > set "CC = clang" in Makefile.am would work, however, I forgot it. But the best way to do it would be to pass it to configure, instead of hard-coding it in the Makefile.am: $ ./configure CC=clang Not only this is more flexible, but

Re: How to specify compiler?

2010-09-09 Thread Lyre
Never mind. set "CC = clang" in Makefile.am would work, however, I forgot it. On Thu, Sep 9, 2010 at 2:22 PM, Lyre <417...@gmail.com> wrote: > I would like use clang as the default compiler rather than gcc. Is there an > option to specify it ? >