SDK Compile (using CodeWarrior)

Helper

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

On 24/08/2005 at 20:10, xxxxxxxx wrote:

User Information:
Cinema 4D Version:   9.102
Platform:      Mac OSX ;
Language(s) :     C++ ;

---------
Hi,

When I tried to open SDK workspace using CodeWarrior V9 under Mac OSX V10.4, I'm getting following error message and couldn't able to continue from here:

"Error importing XML file 'cinema4dsdk.dsw' near line 6
Found tag '4' where tag 'MWIDEWORKSPACE' was expected"

And idea why it happens? Sorry, I'm a new swimmer under Mac Development.

Helper

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

On 25/08/2005 at 01:08, xxxxxxxx wrote:

.DSW is for VC on Windows, you want to use the .prj file.

Helper

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

On 25/08/2005 at 01:39, xxxxxxxx wrote:

I couldn't able to open cinema4dsdk.prj which is disabled when I went thro' File->Open Workspace. That's the reason why I tried to open .dsw file. But I dont know why .prj is disabled.

Helper

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

On 25/08/2005 at 16:55, xxxxxxxx wrote:

What targets does your CodeWarrior have? You need MacOS Classic target to create Cinema 4D plugins for MacOS.

Helper

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

On 25/08/2005 at 19:31, xxxxxxxx wrote:

When I check under "Target Settings Panels" in CodeWarrior, the "Linker" got following items:

None
MacOS Merger
Macintosh PowerPC
Mac OS X PowerPC Mach-O

Is that what you are referring to? If so, I don't see MacOS Classic over here. Please advice me what should I do to proceed further.

Helper

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

On 25/08/2005 at 19:36, xxxxxxxx wrote:

Just checked this out on my Mac. Don't use 'Open Workspace' as the .prj file is not a workspace - it's a project. Use 'Open...' instead.

Added: Looks like you have the Classic target (MacOS PowerPC).

HTH,

Helper

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

On 25/08/2005 at 20:59, xxxxxxxx wrote:

Thanks.

Helper

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

On 28/08/2005 at 19:41, xxxxxxxx wrote:

Hi,

After I open C4D SDK prj file, I tried to build it which throws out a huge list of errors and warnings. I just wanna check with you, before I compile the SDK in CodeWarrior am I supposed to do any settings? If so, can any one tell me how should I compile SDK using CW in Mac platform? Is there any tutorial available? I found few for VC++ but not for CW

Helper

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

On 28/08/2005 at 21:22, xxxxxxxx wrote:

Most of these should be 'void delete' and 'void delete[]' errors. You'll need to fix "c4d_memory.cpp" in your MacOS C4D SDK as follows:

From:

  
void operator delete(void *p)  
{  
     if (p)  
     {  
          void *temp=p;  
          C4DOS.Ge->Free(temp);  
     }  
}  
  
void operator delete[](void *p)  
{  
     if (p)  
     {  
          void *temp=p;  
          C4DOS.Ge->Free(temp);  
     }  
}

To:

  
void operator delete(void *p) throw()  
{  
     if (p)  
     {  
          void *temp=p;  
          C4DOS.Ge->Free(temp);  
     }  
}  
  
void operator delete[](void *p) throw()  
{  
     if (p)  
     {  
          void *temp=p;  
          C4DOS.Ge->Free(temp);  
     }  
}

And these in "c4d_memory.h"

From:

  
void operator delete(void *p);  
void operator delete[](void *p);

To:

  
void operator delete(void *p) throw();  
void operator delete[](void *p) throw();

Helper

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

On 28/08/2005 at 22:36, xxxxxxxx wrote:

Yes, exactly thats what I'm facing.
Thanks Robert, I'll try to change and build again.