ExtUtils-nvcc

 view release on metacpan or  search on metacpan

lib/ExtUtils/nvcc.pm  view on Meta::CPAN

like. There may be a way to fiddle with the configuration a bit, but I wouldn't
hold my breath.

An alternative may be to create a drop-in cl.exe replacement which parses the
arguments for cl.exe and invokes gcc. If that's not reverse-engineering
reverse-engineered, I don't know what is.

=head2 Visual Studio Command Prompt

When you install Visual Studio (as of Visual Studio 2010), you will get a Start
Menu entry for Visual Studio Command Prompt. You should run your build processes
(i.e. cpan) from one of these command prompts. Among other things, this command
prompt sets all of the necessary environment variables to ensure that the
compiler can be found, and that the compiler can find all the necessary
libraries. This may or may not be necessary for using nvcc directly, but it is
certainly is necessary for the rest of the Perl toolchain to find cl.exe and
friends.


=head1 DIAGNOSTICS



( run in 0.892 second using v1.01-cache-2.11-cpan-49f99fa48dc )