Bart Janssens wrote:
> Good news! Evan's CUDA module builds on Win32 now and can be linked to
> K-3D using MinGW. Basically, the steps are as follows:
> 1. Put all functions that use CUDA in a .h/.c file, declaring them
> using __declspec(dllexport) in the .h file.
This would need to be conditional based on the platform, que no?
> For a more elegant solution, I suggest putting the cuda library of
> step 2 in a subdir of k3dsdk, i.e. k3dsdk/cuda. That way, any modules
> that want to use CUDA can simply include it in the
> TARGET_LINK_LIBRARIES command. I think this has to be a C library,
> otherwise the exported symbols are mangled in a way MinGW can't read.
>
How could this be part of the SDK? These are the plugin-specific
implementations we're talking-about, right?
Cheers,
Tim
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone_______________________________________________
K3d-development mailing list
K3d-development@...
https://lists.sourceforge.net/lists/listinfo/k3d-development
