Skip to main content
it enough to have .m
Source Link
Shebuka
  • 3.3k
  • 1
  • 28
  • 45

You have two options:

  1. Directly use your library by adding it to project in xcode, assign a library search path, assign header search path and incude headers in .mmm objective-c source code that use it.
  2. Add all .c files to be compiled and linked by xcode and incude headers in .mmm objective-c source code that use it.

p.s. if you have used some particular compiler switches you may need to rebuild your libraries to properly target iOS.

You have two options:

  1. Directly use your library by adding it to project in xcode, assign a library search path, assign header search path and incude headers in .mm objective-c source code that use it.
  2. Add all .c files to be compiled and linked by xcode and incude headers in .mm objective-c source code that use it.

p.s. if you have used some particular compiler switches you may need to rebuild your libraries to properly target iOS.

You have two options:

  1. Directly use your library by adding it to project in xcode, assign a library search path, assign header search path and incude headers in .m objective-c source code that use it.
  2. Add all .c files to be compiled and linked by xcode and incude headers in .m objective-c source code that use it.

p.s. if you have used some particular compiler switches you may need to rebuild your libraries to properly target iOS.

Source Link
Shebuka
  • 3.3k
  • 1
  • 28
  • 45

You have two options:

  1. Directly use your library by adding it to project in xcode, assign a library search path, assign header search path and incude headers in .mm objective-c source code that use it.
  2. Add all .c files to be compiled and linked by xcode and incude headers in .mm objective-c source code that use it.

p.s. if you have used some particular compiler switches you may need to rebuild your libraries to properly target iOS.