I upgraded from Mohave to Big Sur and found that homebrew is not working any more. I installed the command line tools using the command xcode-select -install After I run brew list, I get the foll. This page explains how to install and use Homebrew on the macOS system to get missing packages. Homebrew installs the apps you need that Apple didn’t include in their base operating system or app store. How to install Homebrew on macOS package manager. Naturally, you need a Mac. Requirements are as follows: A 64-bit Intel CPU or Apple Silicon CPU.

• /bin/bash -c '$(curl -fsSL Https://raw.githubusercontent.com/Homebrew/install/master/install.sh)' This Worked For Me
• Brew Of Love Witchery
• Brew Osx
• Brew Osxfuse
• Installing A Specific Version Of A Homebrew Package

Now that Homebrew is installed, use it to download a package. The tree command lets you see a graphical directory tree and is available via Homebrew. Install tree with the brew install command: brew install tree Homebrew will update its list of packages and then download and install the tree command. Setup the SDK and write your first Brew app. BREW to Brew MP GET. How to migrate your existing Brew applications to Brew MP. Programming Model GET. Technology guide to the Brew MP programming model. Device Database GET. Find the latest Brew device details. Tech Guides GET. Detailed guides to Brew technologies and functional areas.

PowerShell 7.0 or higher require macOS 10.13 and higher. All packages are available on our GitHubreleases page. After the package is installed, run pwsh from a terminal.

Note

PowerShell 7.1 is an in-place upgrade that removes PowerShell Core 6.x and 7.0.

The /usr/local/microsoft/powershell/6 folder is replaced by /usr/local/microsoft/powershell/7.

If you need to run and older version of PowerShell core side-by-side with PowerShell 7.1, installthe version you want using the binary archive method.

There are several ways to install PowerShell on macOS. Choose one of the following methods:

• Install using Homebrew. Homebrew is the preferred package manager for macOS.
• Install PowerShell via Direct Download
• Install from binary archives.

After installing PowerShell, you should install OpenSSL. OpenSSL isneeded for PowerShell remoting and CIM operations.

Installation of latest stable release via Homebrew on macOS 10.13 or higher

If the brew command is not found, you need to install Homebrew followingtheir instructions.

Now, you can install PowerShell:

Finally, verify that your install is working properly:

When new versions of PowerShell are released, update Homebrew's formulae and upgrade PowerShell:

Note

The commands above can be called from within a PowerShell (pwsh) host,but then the PowerShell shell must be exited and restarted to complete the upgradeand refresh the values shown in $PSVersionTable.

Installation of latest preview release via Homebrew on macOS 10.13 or higher

After you've installed Homebrew, you can install PowerShell. First, install the Cask-Versionspackage that lets you install alternative versions of cask packages:

Now, you can install PowerShell:

Finally, verify that your install is working properly:

When new versions of PowerShell are released, update Homebrew's formulae and upgrade PowerShell:

Note

The commands above can be called from within a PowerShell (pwsh) host,but then the PowerShell shell must be exited and restarted to complete the upgrade.and refresh the values shown in $PSVersionTable.

Installing PowerShell using the Homebrew tap method is also supported for stable and LTS versions.

You can now verify your install

When new versions of PowerShell are released, simply run the following command.

Note

Whether you use the cask or the tap method, when updating to a newer version of PowerShell, usethe same method you used to initially install PowerShell. If you use a different method, opening anew pwsh session will continue to use the older version of PowerShell.

If you do decide to use different methods, there are ways to correct the issue using theHomebrew link method.

Installation via Direct Download

Download the PKG package powershell-7.1.3-osx-x64.pkg from the releases page onto yourmacOS machine.

You can double-click the file and follow the prompts, or install it from the terminal:

Install OpenSSL. OpenSSL is needed for PowerShell remoting and CIMoperations.

Install as a .NET Global tool

If you already have the .NET Core SDK installed, it's easy to install PowerShellas a .NET Global tool.

The dotnet tool installer adds ~/.dotnet/tools to your PATH environment variable. However, thecurrently running shell does not have the updated PATH. You should be able to start PowerShellfrom a new shell by typing pwsh.

Install OpenSSL. OpenSSL is needed for PowerShell remoting and CIMoperations.

Binary Archives

PowerShell binary tar.gz archives are provided for the macOS platform to enable advanceddeployment scenarios. When you install using this method you must also manually install anydependencies.

Install OpenSSL. OpenSSL is needed for PowerShell remoting and CIMoperations.

Note

You can use this method to install any version of PowerShell including the latest:

• Stable release: https://aka.ms/powershell-release?tag=stable
• Preview release: https://aka.ms/powershell-release?tag=preview
• LTS release: https://aka.ms/powershell-release?tag=lts

Installing binary archives on macOS

Installing dependencies

OpenSSL is required for PowerShell remoting and CIM operations. You can install OpenSSL via MacPortsif needed.

Note

MacPorts and Homebrew can have problems when used to together on the same system. However,Homebrew does not have a package for OpenSSL 1.0. For more information, see theMacPorts FAQ.

1. Install the Xcode command-line tools. The Xcode tools are required by MacPorts.

2. Install MacPorts. If you need instructions, refer to theinstallation guide.

3. Update MacPorts by running sudo port selfupdate.

4. Upgrade MacPorts packages by running sudo port upgrade outdated.

5. Install OpenSSL by running sudo port install openssl10.

6. Link the libraries to make them available to PowerShell:

Uninstalling PowerShell

If you installed PowerShell with Homebrew, use the following command to uninstall:

If you installed PowerShell via direct download, PowerShell must be removed manually:

To remove the additional PowerShell paths, refer to the paths section in this documentand remove the paths using sudo rm.

Capture one live view. Note

This is not necessary if you installed with Homebrew.

Paths

• $PSHOME is /usr/local/microsoft/powershell/7.1.3/
• User profiles will be read from ~/.config/powershell/profile.ps1
• Default profiles will be read from $PSHOME/profile.ps1
• User modules will be read from ~/.local/share/powershell/Modules
• Shared modules will be read from /usr/local/share/powershell/Modules
• Default modules will be read from $PSHOME/Modules
• PSReadline history will be recorded to ~/.local/share/powershell/PSReadLine/ConsoleHost_history.txt

The profiles respect PowerShell's per-host configuration. So the default host-specific profileexists at Microsoft.PowerShell_profile.ps1 in the same locations.

PowerShell respects the XDG Base Directory Specification on macOS.

Because macOS is a derivation of BSD, the prefix /usr/local is used instead of /opt. So,$PSHOME is /usr/local/microsoft/powershell/7.1.3/, and the symbolic link is placed at/usr/local/bin/pwsh.

Installation support

Microsoft supports the installation methods in this document. There may be other methods ofinstallation available from other sources. While those tools and methods may work, Microsoft cannotsupport those methods.

Additional Resources

Binary Runtime Environment for Wireless (Brew MP, Brew, or BREW) is an application development platform created by Qualcomm, originally for code division multiple access (CDMA) mobile phones, featuring third-party applications such as mobile games. It is offered in some feature phones (mostly with the similar specifications of a mid to high-end mobile phones) but not in smartphones. Developed in 1999, as a platform for wireless applications on CDMA-based mobile phones, it debuted in September 2001.As a software platform that can download and run small programs for playing games, sending messages, and sharing photos, the main advantage of Brew MP is that the application developers can easily port their applications among all Brew MP devices by providing a standardized set of application programming interfaces. Software for Brew MP enabled handsets can be developed in C or C++ using the freely downloadable Brew MP software development kit (SDK).^[1] The Brew runtime library is part of the wireless device on-chip firmware or operating system to allow programmers to develop applications without needing to code for system interface or understand wireless applications. Brew is described as a pseudo operating system, but not a true mobile operating system. Brew is not a virtual machine such as Java ME, but runs native code.

Software[edit]

For software developers, Brew MP is a full set of application programming interfaces (API) that enables making software and applications in C, C++, Java, and is supported (platform) by an application-specific integrated circuit (ASIC). It has a memory footprint of about 15,900 K (15.9 MB), From Brew 1.x until 2.x (before 2004), it has less memory footprint (around 60kb). Brew also features direct hardware access. Versions before Brew MP ran/relied on REX OS (Qualcomm's own RTOS), while Brew MP uses Brew RTOS (another RTOS for advanced feature phones). Rather than using an interpreter-based code, Brew also relied on its own mobile hardware.

Version history[edit]

Brew 1.0/1.1 (2001–2003)[edit]

Debuted in 2001, it was the very first version of Brew. Originally made for the Kyocera QCP-3035 (which was the very first Brew-enabled phone) and Sharp Z-800. It made use of personal digital assistant-level features (usually for some applications and the ability to run Brew applications). However, it lacks advanced multimedia features and support for Java ME that were available in subsequent versions. It was the only version of Brew to support monochrome screens as support for monochrome screens were removed in Brew 2.0.

Brew 1.1 was the first version of Brew to run Java ME applications. It was available in some Brew-enabled phones in 2002 and early 2003.

Brew 2.0/2.1 (2002–2004)[edit]

Released in the mid-2002, it was installed for most of the Brew-enabled phones in late-2002 until early 2004. It includes support for advanced multimedia playbacks (the ability to play video and audio files, as well as support for 3GPP multimedia formats), connectivity for EV-DO and Bluetooth support, as well as screen savers and other improvements. It also supports MIDP 2.0 on Brew 2.1 and it is backward compatible with Brew 1.x applications.

/bin/bash -c '$(curl -fsSL Https://raw.githubusercontent.com/Homebrew/install/master/install.sh)' This Worked For Me

Brew 3.0/3.1 (2004–present)[edit]

Released in 2004, it was the first version of Brew to have major changes and it has a vast majority of features for mobile phones, such as WiFi connectivity, OpenGL ES 1.0, support for 3G, GPS, QWERTY-based keypads, and support for mobile screens that are higher than 176x220. It is backward compatible with Brew 2.x applications, but not with Brew 1.x applications.

It is also the first version of Brew to support 3D graphics, albeit it only uses software rendering (which also supports JSR 184 for Java ME games). Hardware acceleration is also natively supported via OpenGL ES 1.0 (if a 3D acceleration chip is available).

It was installed on most feature phones in the United States and in other countries since 2005 and it is still supported by a few carriers. It is also used for the Zeebo console in Mexico and Brazil.

Brew 4.0 (2007–2011)[edit]

Released in 2007 until 2011, it was only integrated on very few mobile phones (such as LG enV Touch and the LG Versa). It has only a few improvements and it was later succeeded by Brew MP. It has additional features that are also available in Brew MP, such as accelerometer support and other changes.

Brew MP (2009–present)[edit]

Released in 2009, internally known as Brew 5.0, it has new various features (including SVG images support) and certain improvements and it is backward compatible with Brew 3.x and 4.x applications. It is also the first version of Brew to make certain APIs and legacy files deprecated. It is also the first version of Brew to rely on its own RTOS rather than Qualcomm's own REX OS.

Brew application development[edit]

For testing applications during the development process, the SDK includes a Brew emulator, or starting with Brew version 3.1.5 and above, the Brew Simulator. The Brew environment provides for multiple levels of application signatures. One signature authenticates the developer. Another signature verifies that an application has passed True Brew testing and is bestowed through Intertek. The individual telecommunications operators configure the handsets to either enforce or ignore the presence and verification of this second signature. Brew enabled handsets have a test mode that allows applications to bypass verification of the signature. Qualcomm makes applications that have passed testing available to Brew enabled wireless network operators. The operators are then able to choose which of these applications to make available to end-users on their catalog.

Brew's own signatures is protected by an Electronic Serial Number and a MEID, this means it prevents the unauthorized distribution/sideloading of Brew applications to 3rd-parties rather than carriers. Once the application is downloaded OTA via a Brew-based carrier, the .sig file will automatically generate an electronic serial number to its installed handset.

The Brew emulator, named Brew Simulator, does not emulate handset hardware. Instead, the Brew application is compiled to native code and linked with a compatible Brew runtime library. Because of this, applications cannot be tested for platform bugs related to memory alignment and various firmware related glitches without a Brew handset operating in test mode.

For testing purposes, Brew applications can be transferred using a Universal Serial Bus (USB) or serial cable to any Brew-compatible handset using Brew AppLoader from Qualcomm. A Brew application contains several components which, if not present and valid, cause the application to be automatically deleted on reboot. This includes the compiled binary file, a file which describes the application, the features it uses and permissions requested, a file that contains string and image resources if required, and a file containing the application's digital signature.

Brew applications may be unloaded from a consumer handset to save handset memory space. This is referred to as 'Disable/Restore', and is a requirement of the True Brew Test Process. Saved files are kept intact using Disable/Restore, and it is possible to re-load the application without paying for it again. In a 'Disable' situation, all .bar, .mod, and .sig files are deleted from the handset, while any other files remain in their original place. During the 'Restore' operation, the .bar, .mod, and.sig files are downloaded from the carrier's mobile store, and the previously disabled application will have full functionality remaining. The Disable/Restore process is only available to consumer users once the handset's memory is full.

On May 28, 2008, Qualcomm and Adobe announced a partnership to integrate Adobe Flash Lite as a supported user interface on Brew.

Since March 2006, the least expensive digital signature package for developers costs US$400 for 100 application submissions.^[2]

Brew Of Love Witchery

Business model implications/availability[edit]

Strictly speaking, time to market can take longer with Brew than with Java ME because of Brew's rigorous certification requirements. This certification process may be perceived as an advantage by established software developers because the difficulties associated with testing and development costs create a high cost of entry to developers with low budgets and little time, resulting in less market dilution. Specifically, developers of casual games run less risk of having to compete with freewareworkalikes developed and self-published by hobbyists. However this comes as a cost to the end-user as there is less competition to develop the best solution at the lowest price to the end user.

• After an application is written, it takes two weeks per iteration of True Brew testing (each time the application fails the test).
• Next, negotiations with carrier(s) commence.
• Then, (if successful) the carrier will spend time retesting the application with their own tests on their network.
• Finally, rolling out a new version means starting the process over again.

Differences between Java ME and Brew[edit]

Currently, most developers choose to support both Java ME and Brew, or only Java ME.^{[citation needed]} Java ME may offer a lower cost to market because most carriers allow non-certified Java ME applications to run on their phones. Java ME phones have a larger market share than Brew enabled handsets. Java ME is widely used in Europe, while Brew is primarily used in the U.S. and Japan. Even in the U.S.^{[citation needed]} One of the initial advantages of Brew was that Verizon made it easy to purchase applications from the phone, while most Java ME carriers did not. However, most carriers of Java ME phones now offer easy-to-access purchasing portals.

Owing to its different APIs, Java ME relies on Java's virtual machine (interpreter-based code), which is technically slower than BREW, which uses native C/C++ plus and direct hardware access (especially for games).^[3] Java ME has limited subset of APIs (both for applications and games). However, 3rd-party APIs and implementations (such as MascotCapsule by HI CORPORATION. (3D rendering API) and DoJa/Star by NTT Docomo) are available, but not popular and successful outside Japan (particularly device adoption). BREW (on the other hand), relies on its own APIs and direct hardware access.

Performance for Java ME applications and games are slow than BREW. For 3D games, Java ME uses JSR 184 (M3G), which 3D games that are developed on Java ME are slower (which results in 10 frames per second on some/most handsets) and have limited graphics, while BREW uses either software rendering (if the BREW handset does not have a 3D acceleration chip) or OpenGL ES (which it can take advantage of its performance).^[4]

Brew Osx

Some/few handset manufacturers do not allow to integrate Java ME's virtual machine on a few of their phones.

There are now commercial technologies to fully automate porting from Java ME to Brew. This reduces the entry barrier to produce Brew applications by eliminating the need to develop two versions of the same application in both Java and C/C++.

Device usage and carrier availability[edit]

Brew OS is used by some mobile phone manufacturers and mobile networks, however most often the end-user does not know this since mobile phones running Brew most often lack any Brew OS branding and Brew runs in the background with the custom 'skins' of the mobile phone manufacturer or operator on-top. Brew OS is used by Sprint Nextel, metroPCS, U.S. Cellular, Verizon, Syringa Wireless, Cricket Wireless, and AT&T (in the HTC Freestyle) in the US, KDDI in Japan, KT and SK Telecom in South Korea, China Telecom in China, MOVILNET in Latin America, Sistema Shyam (now MTS) in India, and by the 3 network in much of Europe, the UK and Australia on many mobile phones produced especially for their network.

Because BREW is only offered to mobile networks that operates in CDMA, other countries (with the exception of parts of Europe, the UK and Australia via the 3 network, India, Japan and China) do not have BREW, because they do not have CDMA networks.

Manufacturers such as Huawei, INQ Mobile, Amoi, LG, Samsung Mobile, ZTE, and HTC amongst others use Brew OS in some of their mobile phones and it is featured in 3 UK phones such as the 3 Skypephone, INQ1, ZTE Z431, LG T385 and Huawei u7510 (3 Touch). Tectoy's Zeebo is the only game console to use Brew. Motorola's own T720 as well as the RAZR V3m also use Brew OS.

See also[edit]

• Mobile application development — How Brew stacks up against the alternatives on mobile platforms.
• Java ME - Brew's competitor.

Brew Osxfuse

References[edit]

1. ^SDK & Tools | Brew MP DeveloperArchived 2012-12-17 at Archive.today. Developer.brewmp.com. Retrieved on 2013-07-21.
2. ^Code Signing Certificates for Authentic Document IDs for BREW - Digital Signatures | SymantecArchived February 5, 2009, at the Wayback Machine. Verisign.com. Retrieved on 2013-07-21.
3. ^'Choosing between J2ME and BREW for wireless development - TechRepublic'. TechRepublic. Retrieved 2017-06-21.
4. ^'See the graphical difference between Java and BREW games'. Pocket Gamer. Retrieved 2017-06-21.

External links[edit]

• Official website

Installing A Specific Version Of A Homebrew Package