Swift Package Manager - Distribute an already existing Cocoapod - ios

Question

I want to make my already existing Cocoapods available also as Swift Package.
Here's the thing. One of my pods depending on another, so I added this to my Swift package :
// swift-tools-version:5.0
// The swift-tools-version declares the minimum version of Swift required to build this package.
import PackageDescription
let package = Package(
name: "Luminous",
products: [
// Products define the executables and libraries a package produces, and make them visible to other packages.
.library(
name: "Luminous",
targets: ["Luminous"]),
],
dependencies: [
// Dependencies declare other packages that this package depends on.
// .package(url: /* package url */, from: "1.0.0"),
.package(
url: "https://github.com/andrealufino/Deviice.git",
from: "1.30.2"
)
],
targets: [
// Targets are the basic building blocks of a package. A target can define a module or a test suite.
// Targets can depend on other targets in this package, and on products in packages this package depends on.
.target(
name: "Luminous",
dependencies: [],
path: "Sources"),
.testTarget(
name: "LuminousTests",
dependencies: ["Luminous"]),
]
)
My other question is : why the Example folder is included when the package is installed? Here's the pic.
Moreover, last thing, when I build my project in which I added the package, it fails because it cannot find the module for the dependency. The error is No such module Deviice.
I think I added enough details, if you need more, just ask.

Answer 1

I'll answer about the Deviice not found. The other issues are about local paths.
You can see your package as such (In the next comment, "Package" can be understood as library, but also as an executable, for tests purpose often in the case of "sub packages", or "real executables".
let package = Package(
name: "Luminous", // Name of your package
products: [], // What packages people will see relying on internal sub-packages
dependencies: [], // External packages you relies on
targets: [] // Internal "sub-packages", etc.
)
Each target has a dependencies: [], that's where you put the name of either other targets (which are "internal", or public one, that you stated before in dependencies[].
.target(
name: "Luminous",
dependencies: [], //Put here names of either sub packages OR public package you "called before"
path: "Sources")
In your case:
.target(
name: "Luminous",
dependencies: ["Deviice"],
path: "Sources")
Indeed you wrote yourself:
.testTarget(
name: "LuminousTests",
dependencies: ["Luminous"])
So you stated that it depends on the sub package "Luminous", same logic here with Deviice.
You can use as an example the Package of Alamofire+Image. It uses as an external dependency Alamofire, and put it as such.