Dynamic linking library on macbook.
-
Hi,
No, that's wrong. on macOS it's rather the contrary especially if you want to go through the Mac App Store. IIRC, it should rather be one library per "functionality" e.g. network, file IO, etc.
The static build was a requirement for iOS application before iOS 10 for which they have relaxed that rule.
-
Hi,
No, that's wrong. on macOS it's rather the contrary especially if you want to go through the Mac App Store. IIRC, it should rather be one library per "functionality" e.g. network, file IO, etc.
The static build was a requirement for iOS application before iOS 10 for which they have relaxed that rule.
-
Like I wrote, AFAIK, dynamic libraries are recommended.
Note that nothing stops you from linking statically. You'll get a report from the App Store verifiers to tell you whether there's something wrong.
Note that you also have to take into account the licenses of the libraries you are using and whether static linking has implication like it's the case with Qt.
-
Like I wrote, AFAIK, dynamic libraries are recommended.
Note that nothing stops you from linking statically. You'll get a report from the App Store verifiers to tell you whether there's something wrong.
Note that you also have to take into account the licenses of the libraries you are using and whether static linking has implication like it's the case with Qt.
