Build Loop dev with Mac
This page is only relevant when building the
dev branch with a Mac.
For Browser Build, please see: Build Loop dev with Browser
No matter the method used to build Loop-dev, you are testing development code. Please read this link now before continuing.
There is a script to assist in building the
dev branch. It gives you the option to choose the tip of the
dev branch or to build a lightly tested commit. If you have not used the Build Select Script to build Loop previously, you may want to review that page. The command below can be pasted into the terminal of your Mac. Read the directions in the script.
/bin/bash -c "$(curl -fsSL \
dev branch and the lightly tested branch of
dev have Libre support.
BuildLoopDev Other Branches¶
You can use the BuildLoopDev script to build a specific development branch, other than
dev. See the example below that would build
other-branch, if such a branch existed. This is just an example. You need to substitute the branch you desire for
other-branch. There must be a space after the final quote, followed by a hyphen, another space and then the branch name.
other-branch with the BuildLoopDev script
/bin/bash -c "$(curl -fsSL \
https://raw.githubusercontent.com/loopandlearn/lnl-scripts/main/BuildLoopDev.sh)" - other-branch
While Loop-dev is under active development, you should monitor zulipchat and update frequently.
Checking for updates every week is a good idea. Also - subscribe to all the streams on Loop Zulipchat to make sure you don't miss critical information.
You may choose to download fresh each time you update.
You may prefer to use commands to fetch and pull the latest code without making a new clone.
- Some users like to use GitKraken to assist them (link takes you to a tutorial video).
- Some are comfortable with the command line git commands described on here.
The version of code that shows up under the Loop Settings screen does not change when the
dev branch is modified.
If you need help with your app, the mentors need more information. Please issue a Loop Report when asking for help. Refer to Support for how to issue a Loop Report. If you want to keep track yourself, refer to Identify Loop-dev Version
Identify Loop-dev Version¶
The version of code that shows up under the Loop Settings screen will remain fixed until Loop-dev is released. In order to identify which version of dev you have on your phone, you need the commit.
The commit is identified by a 7-digit alphanumeric code. That code was also appended to the folder name of the downloaded code under Downloads/BuildLoop as shown in the graphic above. You can use finder to view the folder name after the script completes. It also appears in the Loop Report, refer to Support for instructions on issuing a Loop Report. After you issue the Loop Report, look at the workspaceGitRevision number near the beginning of the report.