Re: [I] Improving foldering structure [arrow-swift]

["willtemperley (via GitHub)" <gi...@apache.org>]

willtemperley commented on issue #78:
URL: https://github.com/apache/arrow-swift/issues/78#issuecomment-3405831063

   Maybe we should migrate each sub-project incrementally to flatten the structure?
   
   The current project structure has four Package.swift files. Apart from the root, these are:
   ./Arrow/Package.swift
   ./ArrowFlight/Package.swift
   ./CDataWGo/Package.swift
   
   However these three are not actually used by the CI at all. The root Package.swift references the sources, e.g.:
   
           .target(
               name: "Arrow",
               ...
               path: "Arrow/Sources/Arrow",
               ...
           ),
   but does not actually reference the Package files. This explains why the version mismatch between FlatBuffers in ./Arrow/Package.swift
   
           .package(url: "https://github.com/google/flatbuffers.git", exact: "25.9.23"),
   and ./Package.swift
   
           .package(url: "https://github.com/google/flatbuffers.git", from: "25.2.10"),
   has no effect on the CI.
   
   The main project builds fine because it's using FlatBuffers v25.2.10 but when developing locally, the Arrow subproject (./Arrow/Package.swift) will not compile because the generated FlatBuffers are not compatible with v25.9.23.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org