Commit graph

5 commits

Author SHA1 Message Date
Garth Vander Houwen
81a5a46ae2 Assorted version updates and core data cleanup 2024-07-09 08:08:08 -07:00
Garth Vander Houwen
1e9d48c673 Updated protos 2024-07-07 14:13:41 -07:00
Blake McAnally
a8e4c2a653 bump protos 2024-06-28 21:29:51 -05:00
Blake McAnally
b9061b9fd1 bump protos 2024-06-28 11:12:22 -05:00
Blake McAnally
58da532d32 Extract the generated protobufs into its own Swift package
This change modifies the process for generating and integrating the Meshtastic protobufs into the client application.

* The generated Swift code is now in a local SPM package `MeshtasticProtobufs`
* An Xcode Workspace file `Meshtastic.xcworkspace` was created to more easily manage the new build targets.
* The code generation script for the protos was modified to generate the Swift code into the new location.
* The README.md was updated to reflect these changes.

NOTE: After merging this PR, do not open the project file `Meshtastic.xcodeproj`. You must use the workspace `Meshtastic.xcworkspace`

Extracting out the generated protobuf code into its own library enables several opportunities for the project. This is just a first step, but with some more modularization, a standalone Apple Watch app or other targets starts to become a little bit more achievable to implement.

After extracting the protobufs into a Swift package, I validate these changes by building and running the Meshtastic app to an iPhone 15 Pro Max, and tried changing some settings on a local node. I then messaged back and forth using two local nodes connected to two different iOS devices.
2024-06-28 11:11:01 -05:00