X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-3.5 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD,TW_NV X-Spam-Check-By: sourceware.org Message-ID: <508935CB.4060208@etr-usa.com> Date: Thu, 25 Oct 2012 06:51:23 -0600 From: Warren Young User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: Cygwin-L Subject: Re: real beginer References: <1351031752616-93926.post@n5.nabble.com> <50872610.605@cs.umass.edu> <50873B62.3020601@cs.umass.edu> <1351081031692-93944.post@n5.nabble.com> <1351088027625-93956.post@n5.nabble.com> <508802F5.50506@cs.umass.edu> <1351103114379-93973.post@n5.nabble.com> <1351119720396-93981.post@n5.nabble.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 10/25/2012 1:02 AM, René Berber wrote: > On 10/24/2012 6:02 PM, Trixie wrote: > >> Yes i found it later. It works fine i think. >> Tomorrow I'll try configuring with --enable-cuda-gpu > > You need NVIDIA drivers for an NVIDIA card that supports CUDA, plus > their libraries, and probably their development environment. I don't > think it will work with the version(s) of gcc used in Cygwin. On Windows, the nVidia CUDA C compiler (nvcc) uses cl.exe[1], not gcc, but you can download that as part of Visual Studio Express for Windows Desktop 2012[2]. The CUDA SDK is reportedly[3] compatible with VS 2012 already. Since nvcc uses GCC on Linux, it *may* be possible to arm-twist it into using GCC under Cygwin. The CUDA APIs are C-based, not C++-based, so the ABI should be compatible. A hybrid approach may be possible. You might be able to install Visual Studio and ignore its IDE, keeping it around purely so nvcc can find cl.exe, and do everything from within Cygwin. You might even be able to link the resulting object files to Cygwin GCC-compiled object(s), producing a Cygwin executable. I expect getting this to work will be somewhere in difficulty between getting a purely Cygwin GCC toolchain to work and using the pure Visual Studio toolchain, and closer to the former than the latter in difficulty. Trixie, if you want to continue this topic on this list, you'll need to take one of those latter two paths. But, as a "real beginner," I think you'll find it a lot easier to go down the pure Visual Studio path, at least until you start acquiring clues. ;) [1] http://goo.gl/uhZWd [2] http://goo.gl/i76AO [3] http://goo.gl/Av3Ae -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple