cinema4dsdk issues



  • On 26/04/2016 at 14:36, xxxxxxxx wrote:

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

    ---------
    Hello All,

    I just started playing around with the c++ examples in the sdks, which went really promising at first. I compiled the whole cinema4dsdk, then I managed to isolate one plugin and it worked, but now something has changed and the plugin shows only its tif! No name, no UI, no functionality. I checked the .h, .res and .str files ten times over, but they seem correct...

    What's worse, after recompiling the whole cinema4dsdk (Xcode: "build succeeded") only a couple of plugins are shown (10 to be exact) I'm afraid I messed something up, but is there a way to correct this? Or should I go for a complete fresh install of cinema?😲

    I would also like to know how this could have happened, as to avoid it next time. I am using Xcode 7.2, while I read a lot about 6.x. Should I downgrade Xcode? Xcode 7.2 keeps showing a warning "Update cinema.framework.xcodeproj to recommended settings, which I'm afraid I did, and maybe shouldn't have done...

    Looking forward to any suggestions,
    best regards,
    Hermen



  • On 27/04/2016 at 00:11, xxxxxxxx wrote:

    Hi Hermen,

    XCode 6 is the supported OS X IDE for R17. See the C++ page on developers.maxon.net.

    It's recommended to backup cinema4dsdk before modifying it. Also it's recommended to not modify it in Cinema 4D App folder. It's better to copy it to the User plugins folder and change it there.

    How a plugin can only shows its tif? Do you mean it only shows its icon in the UI?
    What's the type of the plugin you've defined?
    Have you checked if there's any error message in the console?

    You can find cinema4dsdk on the PluginCafe GitHub repository at this page and simply download it.



  • On 27/04/2016 at 09:06, xxxxxxxx wrote:

    Hi Yannick,

    OK, I downloaded the cinema4dsdk and installed it, but then Xcode started complaining it couldn't find the c4d.h , while it was clearly visible in the source directory. Anyway, I decided to go for a complete new install, got the updates, and compiled again.

    Now, from  "Programs/MAXON/cinema 4D R17/plugins" this seems to work. However, as I move
    cinema4dsdk to "/Users/myname/Library/Preferences/MAXON/CINEMA 4D R17_xxxxxx/plugins/ ", as per your suggestion, I still can't get things to work. Xcode complains with various errors related to the cinema.framework bundle:

    cinema4dsdk:
    -"c4d.h' file not found

    cinema.framework:
    - Cp: Users/.../Library/ Application Support/MAXON/c4dapi.py: Permission denied
    - Command /bin/sh emitted errors but did not return a nonzero exit code to indicate failure

    So, to sum up: What's the proper way of setting up cinema4dsdk in the user plugins folder?

    Best regards,
    Hermen

    PS: I read the link: Xcode:Moving Project Folders , but it does't give a solution if you move folders OUTSIDE the programs folder.



  • On 28/04/2016 at 03:24, xxxxxxxx wrote:

    Hi,

    The article Xcode: Moving Plugin Projects for the cinema4dsdk gives all the important steps.

    But the information for MAXON_ROOTDIR isn't complete and this may well be why Xcode doesn't find some files.
    MAXON_ROOTDIR has to be set to the directory of the Cinema 4D application for the cinema.framework lib. In the article just one level is removed to the relative path "../../..".
    But if cinema4dsdk is copied to the users-preferences-plugins folder MAXON_ROOTDIR has to be an absolute path.



  • On 28/04/2016 at 06:58, xxxxxxxx wrote:

    Yes, I figured that out. Just to be on the same par: 
    MAXON_ROOTDIR should point to the folder called "CINEMA 4D R17",  not the "MAXON" folder above it, is it? After changing that, I still get the errors as in my previous post. It can't find c4d.h, for example, which is silly because it's just in the project.

    So I give up, it's working from the ROOTDIR folder and I'll leave it there. When the article is updated to include the user folder, I might try it again, but for now I am happy at least its working. Thanks for your help anyway!

    Regards,

    Hermen
    


  • On 28/04/2016 at 07:18, xxxxxxxx wrote:

    Originally posted by xxxxxxxx

    Yes, I figured that out. Just to be on the same par: 
    MAXON_ROOTDIR should point to the folder called "CINEMA 4D R17",  not the "MAXON" folder above it, is it?

    Yes that's exactly that. MAXON_ROOTDIR should point to the folder of the Cinema 4D application. Not the main MAXON folder.

    Originally posted by xxxxxxxx

    After changing that, I still get the errors as in my previous post. It can't find c4d.h, for example, which is silly because it's just in the project.

    Have you cleaned up the project with Project->Clean? Have you clean up the cinema4dsdk project in the Cinema 4D plugins folder as suggested at the beginning of the article?

    Originally posted by xxxxxxxx

    So I give up, it's working from the ROOTDIR folder and I'll leave it there. When the article is updated to include the user folder, I might try it again, but for now I am happy at least its working. Thanks for your help anyway!

    I've copied a fresh cinema4dsdk, followed the article steps and the project builds without problem.
    The information for MAXON_ROOTDIR just needs to be updated.



  • On 28/04/2016 at 08:04, xxxxxxxx wrote:

    Ok, I guess I must have done something wrong. Good to know the article is correct, and when I have more time I'll give it another try. Thanks for your help!

    regards,

    Hermen


Log in to reply