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

    cinema.framework.xcodeproj locked [SOLVED]

    SDK Help
    0
    3
    281
    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

      On 24/03/2015 at 15:47, xxxxxxxx wrote:

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

      ---------
      I have created a plugin project which references "cinema.framework.xcodeproj" to generate "libcinema.framework.a". With my user account I have read only access to the Cinema 4D "frameworks" folder. When loading my project, Xcode (6.2) always tells me that "cinema.framework.xcodeproj" is locked and if I want to unlock it. Since I don't want to change anything in this project, I always have to answer "Don't unlock". Is there any way to disable that warning and just use the referenced project without unlocking it?

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

        On 25/03/2015 at 15:40, xxxxxxxx wrote:

        Hi beba,

        In your situation, you're triggering operating system security mechanisms that you can't ignore.

        Your only options are:

        1. Unlock it so that it stops nagging you about it, and just be careful about not changing anything in it
        2. Uninstall the SDK and re-install it to a path where it doesn't lock in the first place
        3. Just keep having to answer the question each time

        Sorry, but I doubt there are any other options.

        Joey Gaspe
        SDK Support Engineer

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

          On 02/04/2015 at 10:21, xxxxxxxx wrote:

          I'll assume the above solved the issue, closing this thread as solved.

          Joey Gaspe
          SDK Support Engineer

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