Support for CocoaPods about sqlite.swift HOT 24 CLOSED

I'm in favor of this, but am not sure it's possible at the moment. SQLite.swift uses a bridging header to #include <sqlite3.h>, which typically isn't allowed in framework targets. I tested a podspec briefly and found that because it generates its own targets, umbrella header, etc., it fails to build.

See: CocoaPods/swift#8.

Meanwhile, it's possible to import sqlite3 using a custom modulemap file, but this is problematic because the modulemap must have a hard-coded path to the specific linked/includes header, meaning it would have to generate this map dynamically and/or maintain different import paths for iphoneos, iphonesimulator (perhaps multiple, one per Xcode build), and macosx. CocoaPods would somehow need to have the ability to manage this generation, and SQLite.swift would likely be littered with #if os(...) directives.

An alternative would be to link to libsqlite3.dylib, but maintain our own, public #include "sqlite3.h", but this seems especially problematic and has a high maintenance cost.

In the end this is a deficiency on Apple's end that will hopefully be resolved with the next major developer release, if only with the inclusion of more core system modulemaps.

Here's the spec I tried if others are interested in trying to tackle this:

Pod::Spec.new do |s|
  s.name = 'SQLite.swift'
  s.module_name = 'SQLite'
  s.version = '0.1.0'
  s.summary = 'A type-safe, Swift-language layer over SQLite3.'

  s.description = <<-DESC
    SQLite.swift provides compile-time confidence in SQL statement syntax and
    intent.
  DESC

  s.homepage = 'https://github.com/stephencelis/SQLite.swift'
  s.license = { type: 'MIT', file: 'LICENSE.txt' }

  s.author = { 'Stephen Celis' => '[email protected]' }
  s.social_media_url = 'https://twitter.com/stephencelis'

  s.library = 'sqlite3'

  s.source = {
    git: 'https://github.com/stephencelis/SQLite.swift.git',
    tag: s.version
  }

  s.source_files = 'SQLite Common/**/*.{swift,c,h,m}'

  s.xcconfig = {
    'SWIFT_OBJC_BRIDGING_HEADER' => 'SQLite-Bridging-Header.h'
  }
end

from sqlite.swift.

Thank you very much for your quick and detailed response! It wasn't clear to me that integrating Sqlite.swift in CocoaPods is non-trivial! It is clear that you've detailed knowledge of the problem. I'm sorry but I don't think that I can be of any help in solving it.

from sqlite.swift.

+1 for CocoaPods support!

from sqlite.swift.

@robconrad Unfortunately I don't think it's possible right now, but feel free to file a duplicate radar at https://bugreport.apple.com asking for Apple to include a module map for sqlite3!

from sqlite.swift.

Alright, 0.37 let's us make this happen! 7627523

from sqlite.swift.

sorry, but I found this:

from sqlite.swift.

@k7 Could you please read the contributing guidelines and follow the instructions there? E.g. run a clean build, provide a lot more information, and, if possible, provide a reproducible project? I've installed via CocoaPods using the latest versions of Xcode several times in brand new projects and haven't encountered the issue you're seeing above.

from sqlite.swift.

I am sorry not replying earlier.
Just delete the Xcode Derived Data will fix my problem.

Thank you very much for you doing a lot of work on this.

from sqlite.swift.

@stephencelis Did what you wrote and included the bridging header with: SWIFT_OBJC_BRIDGING_HEADER in the podspec file. I used in the pods bridging header:

#import <TestLib/SomeViewController.h>

After installing the pod the bridging header was not installed correctly the files from the pod where not found.

Here is a stackoverflow question on this: http://stackoverflow.com/questions/30608575/include-pods-bridging-header-to-build-settings

from sqlite.swift.

@steffimueller That's an ooold comment. Check out the current pod spec in the repo proper: https://github.com/stephencelis/SQLite.swift/blob/743530d1e56c86b5cd4df5153839a98ecb05bf5f/SQLite.swift.podspec

(Particularly the custom module map.)

from sqlite.swift.

This does not answer my question. Or could you please point to the correct position?

from sqlite.swift.

@steffimueller Not sure what you're asking. I linked directly to a working podspec. I also answered your StackOverflow question.

from sqlite.swift.

Well, thank you. The Stackoverflow question is not about pod Swift frameworks. It is just about pure Objective pods. Could you please update your answer on that. Thank you so much.

from sqlite.swift.

@steffimueller That's confusing. Bridging headers are for bridging code into Swift. They do not make any sense for pure Objective-C pods.

from sqlite.swift.

My pod is pure Objective-C but the project the pod ist installed in is Swift.

from sqlite.swift.

What I want to say is that there is just no Swift code in the Pod.

from sqlite.swift.

@steffimueller Then why would you need a bridging header in your pod? Projects that use your pod just need to import your pod's headers in the project's bridging header to make them available to Swift.

from sqlite.swift.

I want to skip the projects bridging header and ship the pod with a pre configured bridging header.

from sqlite.swift.

@steffimueller You can't and shouldn't. End-developers, at the moment, are expected to manage their own bridging headers. As a pod maintainer you do not (and should not) have the ability to modify their bridging header or project settings.

from sqlite.swift.

That is why I want to create a separate bridging header in my pod.

from sqlite.swift.

@steffimueller I'm trying to explain that doing so (even if it were possible) would not give you the ability to do what you want.

Think of it this way: you are working on an app. It's written in Swift, mostly, and you want to use an Objective-C pod. You install the pod and manually type #import <ThePod/ThePod.h> into your bridging header, as instructed by the pod's installation instructions.

The pod, if it could include a bridging header, would use it to import private Objective-C code directly into Swift. This is not currently possible, but it also doesn't accomplish what you want to do. A pod's bridging header would not propagate down into your app. The modules are separate.

from sqlite.swift.

Okay so it is impossible?

from sqlite.swift.

@steffimueller Nope. Clarified in previous comment.

from sqlite.swift.

Thanks for help.

from sqlite.swift.