xchammer
xchammer copied to clipboard
bazel-xcode
XCHammer generates Xcode projects from a Bazel Workspace.
We currently generate projects during the build if needed. In addition, it'd be awesome to have a program that watches for changes in files, and updates projects for me.
After running `make workspace` the generated Xcode project for XCHammer it's self, doesn't have this flag. We should eventually use XCHammer to build and develop XCHammer, which will fix this...
When XCHammer was originally implemented, the goal was to version program along with each commit. The point of versioning _every_ tooling dependency is to ensure that a given commit can...
The following directory structure does not get built into the xcodeproject as a localised resource: There was a hard filter to prevent plists from being ingested as resources.
XCHammer was originally designed to produce a great user experience for local on Xcode development. However, building with Bazel is still useful and widely preferred. The current approach to achieving...
Currently we create the bundle targets but they need to be dependencies of top-level targets and copied into the final bundle. Currently this does not happen.
Improve CLI messages for workspace generation. Consider adding: - colors to indicate failures or success - emojis to give it a fun and friendly feel - print the name of...
It is certain that XCHammer works on a subset Bazel versions and the integration test suite should prove that. If a user provides a version number outside of our known...
Loading `xcodeproject.bzl` loads `tulsi.bzl` which references `@xchammer_tulsi_aspects//:tulsi/tulsi_aspects.bzl`. Am I doing something wrong or does this not exist?
I have a project that builds and runs fine when executed from bazel, but fails with the below error when the generated project is run in xcode: ``` error: Unexpected...
Metadata
Owner
Metadata
XCHammer generates Xcode projects from a Bazel Workspace.