Google Git
Sign in
bazel / tulsi / b7831ca9707fda4f46b158408e0d099360c71f6e
commitb7831ca9707fda4f46b158408e0d099360c71f6e[log] [tgz]
authornglevin <nglevin@google.com>Mon Apr 09 16:19:19 2018 -0400
committerSergio Campama <sergiocampama@gmail.com>Wed Apr 11 17:58:33 2018 -0400
tree2571ac23f96a3c49875e888b2633a38504b3cdfd
parent55f20080a84ed2761a3e386e0f82f32cb9321b1a [diff]
Remove main_group_path from bazel_build.py

This has been equivalent to the workspace root for some time, via
TULSI_WR defined as an Xcode user-defined environment variable.

Since TULSI_WR typically references an absolute path to the WORKSPACE
that the generated Xcode project was based on, or references the Xcode
variable $SRCROOT (for more info see
https://pewpewthespells.com/blog/buildsettings.html#srcroot) both of
which are the foundation of all source code made visible to Xcode, the
use of this variable seems redundant, and the comment about debug
information is significantly out of date.

In addition, -fdebug-prefix-map is not supported on Xcode 7, which is
where -fdebug-compilation-dir was last available.

Given that we've used -fdebug-prefix-map as a public default for some
time, and we don't support Xcode 7, it makes more sense to me to
remove its reference entirely, along with other conditional code
assuming the use of Xcode < 8.

PiperOrigin-RevId: 192176379
1 file changed
tree: 2571ac23f96a3c49875e888b2633a38504b3cdfd
  1. site/
  2. src/
  3. .gitignore
  4. AUTHORS
  5. CONTRIBUTING.md
  6. CONTRIBUTORS
  7. LICENSE.txt
  8. README.md
README.md

Tulsi - an Xcode Project Generator For Bazel

Building and installing

  1. Open src/Tulsi.xcodeproj, and within Xcode, build the TulsiApp.

  2. Run the TulsiApp.

Notes

Tulsi-generated Xcode projects use Bazel to build, not Xcode via xcbuild. This means that many common components of an Xcode project are handled differently than you may be used to. Notable differences:

  • BUILD files are the source of truth; most changes made to your Xcode project won't affect the build.
    • Adding new sources to the Xcode project won't include them in your app; they must be added to BUILD files.
    • Changes made to your BUILD files, such as adding new library dependencies, are incorporated automatically when building your generated project. The only time you need to re-run Tulsi is if you want to add additional build targets or have new source files show up in Xcode for editing.
    • The Info.plist file is governed entirely by BUILD rules in Bazel and is not displayed in the Xcode UI.
    • Changes to compilation flags (i.e. -DHELLO) should be made in the BUILD files in order to affect the build; changes made to compilation settings in the Xcode UI will only affect indexing. You may want to regenerate your project using Tulsi after modifying compilation flags.