[Bf-committers] [Bf-blender-cvs] SVN commit: /data/svn/bf-blender  branches/cycles/intern/cycles/ cmake/external_libs.cmake: Cycles:
ideasman42 at gmail.com
Mon Oct 17 03:28:31 CEST 2011
Yep, find_package looks the way to go since cuda has a module for this,
even if this didn't exist you could use find_program rather then
having hard coded paths.
On Mon, Oct 17, 2011 at 11:11 AM, Alex Opazo <stargeizer at yahoo.com> wrote:
> 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.
> 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 <blender at dingto.org>
> To: bf-blender developers <bf-committers at blender.org>
> Sent: Sunday, October 16, 2011 7:18 PM
> Subject: Re: [Bf-committers] [Bf-blender-cvs] SVN commit: /data/svn/bf-blender  branches/cycles/intern/cycles/ cmake/external_libs.cmake: Cycles:
> 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.
> 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
>> Bf-committers at blender.org
More information about the Bf-committers