rules_xcodeproj VS XcodeGen

(2b) fork flutter_tools to work with Bazel (like you forked the engine)

Each of these is quite a lot of work. I'm curious to hear what you think about this.

[0]: https://github.com/MobileNativeFoundation/rules_xcodeproj

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive") http_archive( name = "com_github_buildbuddy_io_rules_xcodeproj", sha256 = "564381b33261ba29e3c8f505de82fc398452700b605d785ce3e4b9dd6c73b623", url = "https://github.com/buildbuddy-io/rules_xcodeproj/releases/download/0.9.0/release.tar.gz", ) http_archive( name = "cgrindel_rules_spm", sha256 = "03718eb865a100ba4449ebcbca6d97bf6ea78fa17346ce6d55532312e8bf9aa8", strip_prefix = "rules_spm-0.11.0", url = "https://github.com/cgrindel/rules_spm/archive/v0.11.0.tar.gz", ) load( "@cgrindel_rules_spm//spm:defs.bzl", "spm_pkg", "spm_repositories", ) load( "@cgrindel_rules_spm//spm:deps.bzl", "spm_rules_dependencies", ) spm_rules_dependencies() load( "@com_github_buildbuddy_io_rules_xcodeproj//xcodeproj:repositories.bzl", "xcodeproj_rules_dependencies", ) xcodeproj_rules_dependencies() load( "@build_bazel_rules_apple//apple:repositories.bzl", "apple_rules_dependencies", ) apple_rules_dependencies() load( "@build_bazel_rules_swift//swift:repositories.bzl", "swift_rules_dependencies", ) swift_rules_dependencies() load( "@build_bazel_rules_swift//swift:extras.bzl", "swift_rules_extra_dependencies", ) swift_rules_extra_dependencies() load( "@build_bazel_apple_support//lib:repositories.bzl", "apple_support_dependencies", ) apple_support_dependencies() spm_repositories( name = "swift_pkgs", platforms = [ ".macOS(.v10_15)", ], dependencies = [ spm_pkg( url = "https://github.com/apple/swift-log.git", exact_version = "1.4.2", products = ["Logging"], ), spm_pkg( url = "https://github.com/pointfreeco/swift-composable-architecture.git", exact_version = "0.43.0", products = ["ComposableArchitecture"], ), spm_pkg( name = "Bow", url = "https://github.com/bow-swift/bow.git", exact_version = "0.8.0", products = ["Bow", "BowEffects", "BowOptics"], ), spm_pkg( url = "https://github.com/grpc/grpc-swift.git", exact_version = "1.7.3", products = ["GRPC"], ), spm_pkg( url = "https://github.com/hyperoslo/Cache", exact_version = "6.0.0", products = ["Cache"], ), ], )

Worth noting if project file changes would be pretty common in the development flow then maybe using a regen tool would be useful to prevent major conflicts, I’d recommend https://github.com/yonaskolb/XcodeGen

There are a lot of tools and solutions that can help manage a large codebase. For example, a good CI/CD system linked to GitHub or your internal source control system can ensure that all of your unit tests and UI tests run on every PR and block PRs from merging if there are test failures. And if the company chooses not to check in the .xcodeproj or .xcworkspace file, but rather rely on project autogeneration tools like xcodegen, then you can eliminate annoying merge conflicts in PRs that happen when two teams happen to touch files that are near each other in the .pbxproj file (but at the cost of developers always having to run xcodegen when checking out a new branch).

`git clone https://github.com/yonaskolb/XcodeGen.git cd XcodeGen make install`

Parent comment is right, but check out XcodeGen and get away from the project file. It’s an abomination.

I don't see anything wrong with your gitignore. If this is causing too many problems, have you considered using a tool that will generate xcodeproj files for you, like XcodeGen?

Curious why you guys built XCodeJS instead of going with XcodeGen or Tuist

It's such trash. For my personal projects, XcodeGen is a lifesaver.

How Apple thinks that a single god file is a good idea is crazy to me. No other build tool needs this.

https://github.com/yonaskolb/XcodeGen