Closed GoogleCodeExporter closed 8 years ago
This is not a Thrust issue.
You need to ensure that all your project's source files are compiled with
consistent code generation options such that the same MS runtime library is
linked in.
Original comment by jaredhoberock
on 9 Mar 2011 at 6:30
All the sources ARE compiled with consistent code generation.
Please try the "marching cube" example in the cuda 4.0, there is only 2 source
files.
By default they are compiled with /MT -> no problem
and now try to compile them with /MD -> link errors
There is no problem when no Thrust files are included. And the same code is
working correctly with cuda 3.2 + Thrust 1.3.
So please reconsider the question ;)
Original comment by matthieu.nesme@gmail.com
on 10 Mar 2011 at 8:14
Actually I simply tried to compile it with cuda 3.2 and the Thrust library
distributed in the cuda 4.0 RC toolkit and it is working.
So you should have right, it is not a Thrust issue.
Do you think the problem can come from cuda 4.0 nvcc?
Original comment by matthieu.nesme@gmail.com
on 10 Mar 2011 at 8:27
It's possible this is an nvcc issue.
Original comment by jaredhoberock
on 10 Mar 2011 at 7:03
Original issue reported on code.google.com by
matthieu.nesme@gmail.com
on 9 Mar 2011 at 12:53