Re: Download Visual Studio Code Homebrew
Hercules Montero
I was working to create a custom code studio that leverages Homebrew to enable experimentation for web app development and allow the end user of the code studio to install OS level packages in the container.
Question: Right now I install homebrew in the standard location /home/linuxbrew/. However, when the code studio is stopped this gets deleted and we lose all of the packages that were once installed. Do you know of a way we can keep the installed packages when the code studio is stopped?
task build (from any of the example folders) should work the same as running make clean; make in your terminal.
This should also be the same as doing the Terminal->Run Build Task (Cmd-Shift-B) menu option.
Also, it is possible to use VS Code for editing the code, and running the debugger without using the tasks for compiling. (I personally have the habit of manually running the make commands myself, but still using VS code / Cortex Debug to attach the debugger.
The debugging uses openocd also installed via the Toolchain links above (and the older install.command/homebrew method).
This appears to be finding an older version of openocd. I assume this is because, on M1 homebrew installs to usr/local/opt/homebrew. Should I be trying to install an older version of libusb, or somehow point the tools to the new version of openocd?
I recently got the new Apple Silicon Mac (aka the M1 mac), which means having to deal with the pain points of buying the first generation of something product. Though things are slowly improving, there are still many gotchas when it comes to using the first generation of a product. Installing Intel-based packages using Homebrew on the M1 mac ended up being one such pain for me.
Rosetta 2 sadly does not come pre-installed, and we have to install it explicitly. The user gets prompted to install Rosetta when installing an Intel-based application. However, since I was working mostly in the terminal, I did not get the prompt to do so. I installed it using the terminal itself.
Though Homebrew has been updated for the ARM architecture, it does not simply work out of the box with the architecture as it does with the Intel-emulated Rosetta. I kept getting errors like the one below on brew when trying to install an application that was not available for the M1 architecture:
The two locations live independently of one another: /usr/local for rosetta-emulated (Intel) code and /opt/homebrew for ARM64. These are somewhat hardcoded locations for Homebrew, and there is not much we can do about it.
There are a couple of ways to do this: Creating a different terminal for Rosetta-related stuff and doing it in the same terminal, and adding a few aliases. I prefer the latter, but it is up to you what you choose to do.
Having two terminal applications is never fun. It would be great to do everything in one application, and who likes doubling their own work? Rosetta gives us the ability to prefix commands with the arch -x86_64 prefix to run applications in the emulated mode. And this solves our problems!
d3342ee215