9.1 SDK errors in CodeWarrior 9



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

    On 19/02/2005 at 07:50, xxxxxxxx wrote:

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

    ---------
    Howdy,

    I get these errors in trying to compile the 9.1 SDK in CodeWarrior 9:

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

    Error   : undefined identifier '__register_fragment'
    c4d_pmain.cpp line 121        fragmentID = __register_fragment( __code_start__, __code_end__, __data_start__, __data_end__, __exception_table_start__, _

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

    The first error "the file 'NMWException.h' cannot be opened" is most likely causing the other errors. But, when I check the Access Paths in CodeWarrior, it seems to be fine. I did a search in the finder for the file "NMWException.h" and there are three of them. One in the MacOS Support folder, one in the MacOSX Support and one in the Win23-x86 Support folder. Obviously, I don't need the one in the windows folder on the Mac, but why can it not open the one from the MacOS Support access path? I added a path directly to the file itself and it still cannot open it.

    Any ideas?

    Adios,
    Cactus Dan



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

    On 26/02/2005 at 18:55, xxxxxxxx wrote:

    Howdy,

    Well, I don't know why I got that error. I just went back to try it again and now it compiled, and I didn't change anything from the last time. Oh well, must have been the Heinzelmännchen.

    Adios,
    Cactus Dan


Log in to reply