[CMake] Setting up dependencies for non C++ files.

Abe Stephens abe at sci.utah.edu
Tue Nov 20 14:00:11 EST 2007


If you can get a list of dependencies from the shader compiler, it's  
possible to parse that list into something cmake can use. We did this  
with the output of "nvcc -M" for FindCuda.cmake:

https://code.sci.utah.edu/svn/people/abe/code/CMake-cuda/CMake/cuda/make2cmake.cmake

Abe

On Nov 20, 2007, at 10:44 AM, James Bigler wrote:

> Do you have a link to your cuda stuff that you would be willing to  
> share with this guy on the mailing list?
>
> I don't know if his question is cuda specific, but I think your  
> project would be a helpful reference.
>
> James
>
> Begin forwarded message:
>
>> From: "Josef Karthauser" <joe.karthauser at geomerics.com>
>> Date: November 20, 2007 10:36:16 AM MST
>> To: <cmake at cmake.org>
>> Subject: [CMake] Setting up dependencies for non C++ files.
>>
>> We've got a load of 'shader' files which need to be compiled.  I've  
>> added custom targets for them, however like .cpp and .h files they  
>> have #include directives in as they can include other files.  Is  
>> there an easy way of utilising cmake's dependency checking stuff to  
>> get it to track these dependencies as if they were .h files?
>>
>> Joe
>> _______________________________________________
>> CMake mailing list
>> CMake at cmake.org
>> http://www.cmake.org/mailman/listinfo/cmake
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://public.kitware.com/pipermail/cmake/attachments/20071120/60c55394/attachment.html


More information about the CMake mailing list