@reekon-tools/react-native-pdf-canvas 0.1.0

package/PdfCanvas.podspec

@@ -0,0 +1,80 @@
+require "json"
+
+package = JSON.parse(File.read(File.join(__dir__, "package.json")))
+
+# The pod is named `PdfCanvas`, matching the JS-side native module name, so
+# `NativeModules.PdfCanvas`, `RCT_EXPORT_MODULE(PdfCanvas)`, the Android
+# `PdfCanvasModule.NAME` and the line in `Podfile.lock` are all the same word. A
+# `pod install` that does not print it means autolinking never saw this file — see
+# `react-native.config.js`, which names it explicitly for the same reason the
+# Android entry names its `packageImportPath`.
+Pod::Spec.new do |s|
+  s.name         = "PdfCanvas"
+  s.version      = package["version"]
+  s.summary      = package["description"]
+  s.description  = <<-DESC
+    The iOS rasterizer for @reekon-tools/react-native-pdf-canvas: PDF pages as
+    RGBA bytes at exact doc-space rects, through CoreGraphics for tiles and PDFKit
+    where annotations have to be composited.
+  DESC
+  s.homepage     = "https://gitlab.com/reekon-tools/software/rock-pro/react-native-pdf-canvas"
+  s.license      = { :type => "MIT" }
+  s.authors      = { "REEKON Tools" => "hello@reekon.tools" }
+  s.source       = { :git => "https://gitlab.com/reekon-tools/software/rock-pro/react-native-pdf-canvas.git", :tag => "#{s.version}" }
+
+  # 13.0 rather than the app's 16.4. Nothing here needs anything newer:
+  # `CGPDFDocument`, `CGBitmapContext` and `PDFKit` on iOS all predate it, and
+  # `-[NSFileHandle readDataUpToLength:error:]` — the newest API touched — is 13.0.
+  # `ios/Package.swift` declares the same floor, so the host-machine build and the
+  # pod build agree about what is reachable.
+  s.platforms    = { :ios => "13.0" }
+  s.requires_arc = true
+
+  # PDFKit and CoreGraphics are the whole dependency list. Note what is NOT here:
+  # UIKit. `PdfCanvasCore` is compiled for macOS by `ios/Package.swift` so that
+  # `swift test` can prove it on a laptop, and a UIKit import would break that
+  # build — which is exactly when it should break.
+  s.frameworks   = "PDFKit", "CoreGraphics", "CoreFoundation"
+
+  # THREE TARGETS' WORTH OF SOURCE, ONE POD, mirroring the three source sets
+  # `android/build.gradle` splits with its `standalone` flag:
+  #
+  #   PdfCanvasCore   — the React-free rasterizer. Also a SwiftPM target.
+  #   PdfCanvasSlots  — the raster transport's storage. Also a SwiftPM target,
+  #                     because it guards `<jsi/jsi.h>` with `__has_include`; this
+  #                     build is the one where that header IS present, so the host
+  #                     function is compiled in.
+  #   PdfCanvasBridge — the React binding. Only ever built here: it needs
+  #                     `<React/RCTBridgeModule.h>` and
+  #                     `<ReactCommon/RCTInteropTurboModule.h>`.
+  s.source_files = "ios/Sources/**/*.{h,m,mm}"
+
+  # Both `include` directories, so `#import <PdfCanvasRasterizer.h>` resolves from
+  # the bridge and `#import "PdfCanvasSlots.h"` resolves from itself. Angle-bracket
+  # imports of a pod's own headers are what survives `use_frameworks!`, which this
+  # package's first consumer uses (`ios.useFrameworks: static`).
+  s.pod_target_xcconfig = {
+    "HEADER_SEARCH_PATHS" => [
+      '"$(PODS_TARGET_SRCROOT)/ios/Sources/PdfCanvasCore/include"',
+      '"$(PODS_TARGET_SRCROOT)/ios/Sources/PdfCanvasSlots/include"',
+      '"$(PODS_TARGET_SRCROOT)/ios/Sources/PdfCanvasBridge/include"',
+    ].join(" "),
+    # C++17 is the floor `<jsi/jsi.h>` needs; the React Native podspecs in the
+    # same install compile at 20, and `install_modules_dependencies` below raises
+    # this to match when it is available.
+    "CLANG_CXX_LANGUAGE_STANDARD" => "c++17",
+    "DEFINES_MODULE" => "YES",
+  }
+
+  # `install_modules_dependencies` is React Native's own helper (react_native_pods.rb).
+  # It adds React-Core, React-jsi, ReactCommon/turbomodule and the rest, and sets
+  # the new-architecture compiler flags — so the pod tracks whatever the host's RN
+  # version wants rather than restating a dependency list that would go stale. The
+  # `defined?` guard is what every RN library ships: it lets `pod lib lint` and any
+  # non-RN install still evaluate the podspec.
+  if defined?(install_modules_dependencies) != nil
+    install_modules_dependencies(s)
+  else
+    s.dependency "React-Core"
+  end
+end