Since CMAKE 2.8 devs included a findCUDA script that can be used to detect CUDA cross-platform.
Documentation is here: http://www.cmake.org/cmake/help/cmake-2-8-docs.html#module:FindCUDA And the usage seems to be kinda simple... A simple example can be found at: http://rafaelpalomar.net/blog/2010/jan/22/building-cuda-projects-cmake Hope it helps somehow. J. Caveat emptor: I'm no experienced coder, and i don't use cmake, but a friend that is used to cmake comes with these 2 links. ________________________________ From: Thomas Dinges <[email protected]> To: bf-blender developers <[email protected]> Sent: Sunday, October 16, 2011 7:18 PM Subject: Re: [Bf-committers] [Bf-blender-cvs] SVN commit: /data/svn/bf-blender [41071] branches/cycles/intern/cycles/ cmake/external_libs.cmake: Cycles: Hi, well I call cmake from D drive, so this would not work. If there is a better solution, I can change it (don't know cmake too well). But for now, better than always manually add the path. Regards, DingTo Am 17.10.2011 00:14, schrieb Αντώνης Ρυακιωτάκης: > hmm...C is not always the default drive, maybe something like /Program > Files/NVIDIA GPU Computing Toolkit/CUDA/v4.0 would be better? > (Again making the assumption that cmake is called from the same drive > as the CUDA installation) > _______________________________________________ > Bf-committers mailing list > [email protected] > http://lists.blender.org/mailman/listinfo/bf-committers -- Thomas Dinges Blender Developer, Artist and Musician www.dingto.org _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
