THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 18/04/2008 at 08:43, xxxxxxxx wrote:
Cinema 4D Version: R10-10.5
Platform: Mac OSX ;
Language(s) : C++ ;
The bulk of user issues of late have come from those using my plugin on MacOS 10.5.x (Leopard) wherein we know that Apple did a large bit of work on the Cocoa and Carbon interfaces. I'm currently not using this version of the OS but instead 10.4.12.
My plugin includes the Carbon Framework in order to support some OS functions (mainly to get at archaic Resource Forks). This is the only external OS code used in my plugin. And, thus, it seems to be the most likely suspect since these issues appear to be limited to MacOS and 10.5.x.
If this is the case, how the heck would I go about resolving it?
On 21/04/2008 at 00:20, xxxxxxxx wrote:
I am not sure but as there is currently no 64bit version of Cinema4D for OSX it shouldn't affect you, should it? Afaik Leopard can run Carbon based applications without problems.
On 21/04/2008 at 07:31, xxxxxxxx wrote:
Right. But I'm including the Carbon Framework from 10.4.11 in the build. I'm not certain that any of its code actually becomes part of the plugin and that may conflict with the Carbon Framework of 10.5.2. Or that using Xcode 2.4.1 is good enough. No idea.
I'm attempting currently to find a way to get 10.5.2 and retain 10.4.11 on my iMac in order to test it myself. This would probably require a dual-boot with 10.5.2 on an external drive (as the least expensive alternative).