4 posts tagged with "rules_xcodeproj"

Since the first commit of rules_xcodeproj, we’ve been committed to it being community driven and community owned. Early in rules_xcodeproj’s development, multiple companies started using the project, while also putting forth significant contributions. And all throughout its development we’ve solicited feedback from users on how the project is working for them, not working for them, and what we should be focusing on next.

Today we are taking the next step in this commitment; we are solidifying the community ownership of rules_xcodeproj by donating it to the Mobile Native Foundation!

Today we released version 1.3.2 of rules_xcodeproj!

This is a pretty exciting release, as it adds support for multiple Xcode configurations (e.g. Debug and Release). Since early in rules_xcodeproj’s development, being able to have more than the default Debug configuration has been highly requested. We would have implemented support much sooner, but because rules_xcodeproj accounts for every file path and compiler/linker flag, in order to have rock solid indexing and debugging support, it wasn’t an easy task.

Almost exactly one year ago I wrote the first commit for rules_xcodeproj. Like a lot of software engineers, I’m pretty bad at estimating, and thought that I would be able to finish 1.0 in 2 to 4 months 😅. The longer development cycle was a result of an increased scope and level of quality that I came to expect for a proper 1.0 release. Over the course of the year, I believe the project has risen to meet my expectations, and today I’m happy to announce the release of version 1.0 of rules_xcodeproj!

rules_xcodeproj is a Bazel ruleset that can be used to generate Xcode projects from targets in your workspace. We are happy to announce that today we are releasing the first version of the ruleset, version 0.1.0.