This is an automated email from Gerrit. "Marc Schink <[email protected]>" just uploaded a new patch set to Gerrit, which you can find at https://review.openocd.org/c/openocd/+/9403
-- gerrit commit f10ada0776ee5f3f0867a7abbac538ffd8267df5 Author: Marc Schink <[email protected]> Date: Mon Jan 26 06:58:28 2026 +0100 README.macOS: Align structure and fix linter errors Refactor the document structure to align with README.Windows and fix two line-length issues so that the file is free of Markdown linter [1] errors. [1] https://github.com/jackdewinter/pymarkdown Change-Id: Iab5ca09aeed2225e43934c8c2bd952a3a4b32cd0 Signed-off-by: Marc Schink <[email protected]> diff --git a/README.macOS.md b/README.macOS.md index 2d2399c9ab..cde8d8d1eb 100644 --- a/README.macOS.md +++ b/README.macOS.md @@ -1,4 +1,8 @@ -# Building OpenOCD for macOS +# OpenOCD for macOS + +This README contains instructions that are specific to macOS. + +## Building There are a few prerequisites you will need first: @@ -25,15 +29,18 @@ With Homebrew you can either run: or - brew install libtool automake libusb [hidapi] [libftdi] (to install the needed dependencies and then proceed with the - manual building procedure) + brew install libtool automake libusb [hidapi] [libftdi] + +to install the needed dependencies and then proceed with the manual building +procedure. For building with MacPorts you need to run: sudo port install libtool automake autoconf pkgconfig libusb [libftdi1] You should also specify LDFLAGS and CPPFLAGS to allow `configure` to use -MacPorts' libraries, so run configure like this: `LDFLAGS=-L/opt/local/lib CPPFLAGS=-I/opt/local/include ./configure [options]` +MacPorts' libraries, so run configure like this: +`LDFLAGS=-L/opt/local/lib CPPFLAGS=-I/opt/local/include ./configure [options]` See [README](README.md) for the generic building instructions. @@ -47,4 +54,4 @@ for FTDI vendor driver use: sudo kextunload FTDIUSBSerialDriver.kext -To learn more on the topic please refer to the official libusb FAQ: <https://github.com/libusb/libusb/wiki/FAQ> \ No newline at end of file +To learn more on the topic please refer to the official libusb FAQ: <https://github.com/libusb/libusb/wiki/FAQ> --
