3 Replies
      Latest reply on Nov 7, 2019 10:17 AM by UbiApple
      UbiApple Level 1 Level 1 (10 points)

        I have a client who has their own app and would like to include some functionality we can provide.

         

        Our code would just be a library with no interface needed.

         

        Is there a way we can give this to them in a closed file/way so they don't see the code but can use it in their app?

         

        Please provide options, thx.

        • Re: dll equivelant
          jonprescott Level 2 Level 2 (80 points)

          The direct equivalent to a Windows dll is a dylib (dynamic library).  Static libraries (.a) are another option that goes way back to the beginnings of Unix.  If you need to supply headers along with the library in order for client code to compile, for Apple, frameworks are a convenient container that can enclose both headers and the dynamic library.  These are all easy to build within Xcode.  If you are targeting iOS, frameworks and static libraries seem to be the best options (not an iOS programmer, just based on what I've learned on various forums and reading Apple documentation).

          • Re: dll equivelant
            edford Apple Staff Apple Staff (785 points)

            The supported way a vendor, such as yourself, can have a client integrate your closed source library is to use an XCFramework. We introduce them and the situations where they are useful in a WWDC session, and the documentation on creating one is in Xcode's Help.

            • Re: dll equivelant
              UbiApple Level 1 Level 1 (10 points)

              ok thanks for the options