64-bit SDK version compatability

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 18/05/2005 at 00:33, xxxxxxxx wrote:

User Information:
Cinema 4D Version:   NA 
Platform:   Windows  ;   
Language(s) :     C++  ;

---------
Srek over at CGTalk made me aware of the new 64-bit version of Cinema 4D and the new SDK support thereby. I'll ask the same question that I asked him, being referred here for an appropriate response.

I currently use 8.207 SDK for my plugin to support a larger audience. Will migration of plugins only be possible with 9.1 SDK or can it be done using earlier SDKs?

Thanks!

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 18/05/2005 at 00:40, xxxxxxxx wrote:

I don't know; that has not been tested afaik. It might work if you adapt the 8.207 API for 64 bit compatibility yourself, using the 9.1 64-bit API as a reference.
But going through all that makes no sense, since there will never be a 64-bit 8.207. A better way would be to compile the 64-bit version against the 9.1 64-bit API and the rest against the 8.207 API. You could still keep all of your source in the same place, just change the paths in the 64-bit project.
If there are any places where things have changed between 8.207 and 9.1 you will have to insert #ifdefs etc. in your code based on API_VERSION.

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 18/05/2005 at 00:59, xxxxxxxx wrote:

Hi Mikael,

Up late are we (well, my time any way)? ;)

Yes, that would be the obvious solution otherwise. Use the 8.207 SDK for 32-bit and the 9.1 64-bit SDK for 64-bit. The only place where I noted a difference was the QT image issue (which may plague me until Apple remedies it - I have no control over the incoming images) and the Alpha bitmap one, which can be diverted accordingly using #if/#else defines.

Thanks