Maxon Developers Maxon Developers
    • Documentation
      • Cinema 4D Python API
      • Cinema 4D C++ API
      • Cineware API
      • ZBrush Python 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

    Problem with MSVC 2008

    Scheduled Pinned Locked Moved SDK Help
    3 Posts 0 Posters 365 Views
    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 Offline
      Helper
      last edited by

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

      On 07/12/2007 at 04:01, xxxxxxxx wrote:

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

      ---------
      Hi Folks,

      I already posted this at CGTalk but nobody could help me there. I'm having trouble compiling the standard sdk project files that come with Cinema 10 in Visual Studio 2008.
      When I open the project file (cinema4dsdk.vcproj) in the plugin folder it converts the VC++ 6 files to VC++ 9 and loads the sourcecode of the sdk plus the _api project from the recource folder as expected. Now when I try to build the api compiles fine, while for every file in the sdk it claims that c4d.h could not be found. When checking I actually found out that c4d.h is for whatever reason not part of the _api project though it is located in the api sourcecode folder. After adding it to the project and rebuilding I get the same result.
      When I replace the dynamic reference in the sdk code from #include "c4d.h" to a static reference like #include "mydrive:\Programme\MAXON\CINEMA 4D R10\resources\api\c4d.h" it finds the header file but then runs into trouble whenever the next .h file is included from the _api sources.
      I thought that having the _api project file added to the sdk project with dependencies and build order set would be enough to give the compiler a rought idea where it might have to look for the header files, but yet I stay corrected. Is there possibly something I'm missing, like some hidden menu where I have to define additional globals on where those files are located or is it a specific problem that comes up when I convert an VC++ 6 project to a VC++ 9.
      Would be great if someone much wiser than me could help me out on this problem because I get the feeling that this is just a very stupid mistake I'm making.
      Thanks in advance.

      Sparkle

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

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

        On 07/12/2007 at 07:22, xxxxxxxx wrote:

        Nevermind the whole thing, I just figured it out. Apperantly the include directories were inherited from god knows where and the $(WebDeployPath) makro command was used for root location. This didn't seem to work (which I now recall seeing in the compliler optput), so I referenced all the directories again and it works fine.
        I knew it had to something simple.

        Cheers,
        Sparkle

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

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

          On 07/12/2007 at 10:24, xxxxxxxx wrote:

          R10 comes with a VS2005 project for the api lib and the sdk examples. Why not use them? It is recommended - read the C++ SDK documentation:

          We recommend using Visual Studio 2005 or higher on the PC and XCode 2.4.1 or higher on the Mac.

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