THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 08/01/2007 at 07:36, xxxxxxxx wrote:
Cinema 4D Version: 9.6
Platform: Windows ; Mac OSX ;
Language(s) : C++ ;
I've just successfully compiled a x64 version of my plugin. The migration file tells something about "fat" archives:
It is *.cdl64 instead of *.cdl. This will allow you to create "fat" archives - including Mac, Win and Win64 versions of your plugin.
How can this "fat" cdl64 file be created? The cdl64 from Visual 2005 doesn't run with C4D 32Bit.
On 08/01/2007 at 08:59, xxxxxxxx wrote:
I think that this means that by individualizing the file extensions for the various plugin compiles (.cdl, .xdl, .cdl64, .dylib), you can include all of them together in a single archive or install since they will not collide with each other in naming. If they hadn't changed the extension, you couldn't include a Windows 32-bit and 64-bit together unless you named them differently (myplug.cdl and myplug64.cdl, for instance).
On 08/01/2007 at 09:34, xxxxxxxx wrote:
BTW: The C4D R10 demo doesn't run 64Bit native, isn't it? My cdl64 plugin won't be loaded, and the debugger outputs Win32 threads closing when closing. So there isn't any way to test 64Bit plugins with R10 demo!
On 08/01/2007 at 11:35, xxxxxxxx wrote:
As far as I know, no, the R10 demo is Windows 32-bit only. It appears that the 64-bit version is only included with purchase. You might be able to get the core R10 at a good price - best to call your local Maxon dealer.
On 09/01/2007 at 03:24, xxxxxxxx wrote:
Yes, at the moment the demo is 32 bit only. I agree that it would be nice for developers to have a 64bit demo.