Maxon Developers Maxon Developers
    • Documentation
      • Cinema 4D Python API
      • Cinema 4D C++ API
      • Cineware API
      • ZBrush GoZ API
      • Code Examples on Github
    • Forum
    • Downloads
    • Support
      • Support Procedures
      • Registered Developer Program
      • Plugin IDs
      • Contact Us
    • Categories
      • Overview
      • News & Information
      • Cinema 4D SDK Support
      • Cineware SDK Support
      • ZBrush 4D SDK Support
      • Bugs
      • General Talk
    • Unread
    • Recent
    • Tags
    • Users
    • Login

    Codewarrior 10

    SDK Help
    0
    21
    11.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • H
      Helper
      last edited by

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

      On 02/11/2005 at 13:24, xxxxxxxx wrote:

      since 3 hours i try to find the place, where i should change MWException.h instead of NMWException.h.
      i cant find it. the c4d_pmain.cpp doesn't include one of the files above.
      if i make a search through the whole project files, the result is 0!

      can you tell me, where i should change the include ?

      1 Reply Last reply Reply Quote 0
      • H
        Helper
        last edited by

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

        On 02/11/2005 at 13:33, xxxxxxxx wrote:

        Well, if your plugins compile they should probably work fine without any changes. The programmers said that the change was necessary for them to get it to compile in CW10, but perhaps this backward compatibility bug has been fixed in your copy. Anyway, have a look on line 36 of c4d_pmain.cpp in R9.101 and see if changing it makes any difference at all:

            
            
              
            #include <NMWException.h>  
            
        
        1 Reply Last reply Reply Quote 0
        • H
          Helper
          last edited by

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

          On 03/11/2005 at 13:55, xxxxxxxx wrote:

          ahh i found the reason: i test it with 9.1, but i compile it width my old 8.5 sdk, so that they can use it too. and there is no #include <NMWException.h> - no wonder, why i cant find it !

          1 Reply Last reply Reply Quote 0
          • H
            Helper
            last edited by

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

            On 15/11/2005 at 14:19, xxxxxxxx wrote:

            Hope you can give me a hand.
            I just updated to CW 10, and had the same error with the NMWExeption.h mentioned above.
            After changing the line 36 in c4d_pmain.cpp to #include <MWException.h> I still get these errors with C4D v9.1:

            Error   : the file 'MWException.h' cannot be opened
            c4d_pmain.cpp line 36    #include <MWException.h>

            Error   : undefined identifier '__register_fragment'
            c4d_pmain.cpp line 121   __, __exception_table_start__, __exception_table_end__, __RTOC());

            Error   : undefined identifier '__unregister_fragment'
            c4d_pmain.cpp line 153        __unregister_fragment( fragmentID );

            Build of target "CINEMA4D SDK (Debug)" in project "cinema4dsdk.prj" failed because a subtarget or subproject build failed

            Any ideas?

            1 Reply Last reply Reply Quote 0
            • H
              Helper
              last edited by

              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!

              1 Reply Last reply Reply Quote 0
              • H
                Helper
                last edited by

                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.

                1 Reply Last reply Reply Quote 0
                • H
                  Helper
                  last edited by

                  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

                  1 Reply Last reply Reply Quote 0
                  • H
                    Helper
                    last edited by

                    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...

                    1 Reply Last reply Reply Quote 0
                    • H
                      Helper
                      last edited by

                      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

                      1 Reply Last reply Reply Quote 0
                      • H
                        Helper
                        last edited by

                        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.

                        1 Reply Last reply Reply Quote 0
                        • H
                          Helper
                          last edited by

                          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

                          1 Reply Last reply Reply Quote 0
                          • H
                            Helper
                            last edited by

                            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.

                            1 Reply Last reply Reply Quote 0
                            • H
                              Helper
                              last edited by

                              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.

                              1 Reply Last reply Reply Quote 0
                              • H
                                Helper
                                last edited by

                                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

                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post