|author||Nicholas Levin <email@example.com>||Wed Sep 20 18:51:28 2017 +0000|
|committer||Nicholas Levin <firstname.lastname@example.org>||Wed Sep 20 19:14:09 2017 +0000|
Updates version number to 0.4.168009107.20170920. Significant changes: - Verify that the xcodeproj is generated in a safe location. - Targets-specific BEP JSON files for bazel_build. - Added --verbose flag for more detailed logging. - Adds supports for macos_unit_test and macos_ui_test. - Cleaned up exception error messaging around aspects. -- PiperOrigin-RevId: 169427165 MOS_MIGRATED_REVID=169427165
Open src/Tulsi.xcodeproj, and within Xcode, build the TulsiApp.
Run the TulsiApp.
Tulsi-generated Xcode projects use Bazel to build, rather than Xcode. This means that many common components of an Xcode project are handled differently than you may be used to. For example, the Info.plist file is governed entirely by BUILD rules in Bazel and is not displayed in the Xcode UI. It also means that 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.