Skip to content

Conversation

ezathashim
Copy link

  • added modulemap files

  • not sure if it is better to name the actual product 'libPhoneNumber' or just set the module name to 'libPhoneNumber'

  • I have a workspace with many targets that use watchOS, iOS and macOS

  • with each one, I have a separate framework created that is specific for each target

  • it is really, really annoying if I have to deal with the same framework (libPhoneNumber) that has different names (libPhoneNumbermacOS, libPhoneNumberiOS, etc) because that would force me to use if statements to import a framework if a particular name depending on the current target.

  • I find it easier if the framework name is always the same and just call '@import libPhoneNumber', whether iOS, macOS, watchOS or tvOS

  • an alternative would be to name the 'moduleName' different from the target name, but I find tat more confusing

… target

- added modulemap files
- not sure if it is better to name the actual product 'libPhoneNumber' or just set the module name to 'libPhoneNumber'
…re is a private Apple API called ‘NBPhoneNumberUtil’
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant