Codewarrior 10

Helper

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

On 15/11/2005 at 16:52, xxxxxxxx wrote:

Might I also remind everyone that Rui is sitting here (in the previous topic) with the exact same errors as Arndt!

Helper

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

On 16/11/2005 at 01:42, xxxxxxxx wrote:

Hello,
I just got the solution by Philip:

Open the API project settings (both release and debug) and go to Access Paths. Add
{Compiler}MacOS Support/Libraries/Runtime/(Runtime_Common)
to System Paths.

This works fine for me now.

Helper

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

On 17/11/2005 at 09:20, xxxxxxxx wrote:

I tried to do that and when I open the project, I still get the following messages:

  
The following access path in target "_api_v8 (Debug)" of project "_api_v8.prj" cannot be found:  
{Compiler}MacOS Support/Libraries/Runtime/(Common Sources)  
  
The following access path in target "_api_v8 (Final)" of project "_api_v8.prj" cannot be found:  
{Compiler}MacOS Support/Libraries/Runtime/(Common Sources)

And, when I try to compile, I get these errors:

  
Error: the file 'MWException.h' cannot be opened  
c4d_pmain.cpp line 43      #include <MWException.h>  
  
Error: undefined identifier '__register fragment'  
c4d_pmain.cpp line 132   __, __register_table_start__,__exception_table_end__,RTOC());  
  
Error: undefined identifier '__unregister fragment'  
c4d_pmain.cpp line 170   __unregister_fragment( fragmentID );  
  
Error: the file 'MWException.h' cannot be opened  
c4d_pmain.cpp line 43      #include <MWException.h>  
  
Error: undefined identifier '__register fragment'  
c4d_pmain.cpp line 132   __, __register_table_start__,__exception_table_end__,RTOC());  
  
Error: undefined identifier '__unregister fragment'  
c4d_pmain.cpp line 170   __unregister_fragment( fragmentID );  
  
Could not find or load the file "_api_v8_mac_deb.lib" for target "CINEMA SDK (Debug)" for project "cinema4dsdk_2.prj"

Why am I having all these problems?

Rui Batista

Helper

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

On 17/11/2005 at 09:29, xxxxxxxx wrote:

Error: the file 'MWException.h' cannot be opened
c4d_pmain.cpp line 43 #include <MWException.h>
maybe you should check the path to MWException.h ?
this was one error in my tests...

Helper

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

On 17/11/2005 at 09:58, xxxxxxxx wrote:

The file MWException.h is located at {Compiler}MacOS Support/Libraries/Runtime/(Runtime_Common) and also at {Compiler}MacOS X Support/Libraries/Runtime/(Runtime_Common)
right beside the MWException.cpp file.

Isn't that the correct place?

Rui Batista

Helper

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

On 17/11/2005 at 10:17, xxxxxxxx wrote:

Hi Rui,
please try the follwing thing.
While you are in CW 10 with your project open, double click on the "_api_v8.prj" right next to the list of your source files.
After this, choose Edit>_api_v8.prj (Debug) Settings... and check the Access paths settings there as well (even if the right pass is already in the list). Just click on the MacOS Supprt/Libraries/Runtime/(Runtime_Commmon) entry for the System Paths again and click on the Change... button below. Choose the exact same path again. That did it for me, as it seems that the api itself has to use that path, too.

Helper

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

On 17/11/2005 at 10:23, xxxxxxxx wrote:

YES!!! That did it!!!
Thank you all!!
Oh, by the way, shouldn't it be MacOS X Support, instead of MacOS Support, if I'm compiling for OSX?

Rui Batista

Helper

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

On 17/11/2005 at 10:45, xxxxxxxx wrote:

as i know, cinema plugins are not osx libraries.
so macos should be correct.

Helper

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

On 17/11/2005 at 11:12, xxxxxxxx wrote:

RML is correct. Do NOT expect to be able to use MacOS X routines in plugins. Any from the Carbon lib must be 'OS 9' compatible.

Helper

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

On 17/11/2005 at 11:18, xxxxxxxx wrote:

Okidoki... it was just a curiosity of mine

Rui Batista