Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[macOS] Update flasher binaries from Homebrew bottles #100

Merged
merged 1 commit into from
Aug 26, 2019
Merged

[macOS] Update flasher binaries from Homebrew bottles #100

merged 1 commit into from
Aug 26, 2019

Conversation

fauxpark
Copy link
Member

@fauxpark fauxpark commented Jul 25, 2019

Description

In an effort to keep track of where these binaries are coming from, I've replaced them with ones from the following Homebrew bottles:

https://homebrew.bintray.com/bottles/avrdude-6.3_1.high_sierra.bottle.tar.gz
https://homebrew.bintray.com/bottles/dfu-programmer-0.7.2.high_sierra.bottle.tar.gz
https://homebrew.bintray.com/bottles/dfu-util-0.9.high_sierra.bottle.tar.gz
https://homebrew.bintray.com/bottles/teensy_loader_cli-2.1_1.high_sierra.bottle.tar.gz
https://homebrew.bintray.com/bottles/libusb-1.0.22.high_sierra.bottle.tar.gz
https://homebrew.bintray.com/bottles/libusb-compat-0.1.5_1.high_sierra.bottle.tar.gz
https://homebrew.bintray.com/bottles/libftdi0-0.20.high_sierra.bottle.2.tar.gz

The dylib paths need to be pointing to the right place, so I ran the following:

install_name_tool -change "@@HOMEBREW_PREFIX@@/opt/libusb/lib/libusb-1.0.0.dylib" "@executable_path/../Frameworks/libusb-1.0.0.dylib" avrdude
install_name_tool -change "@@HOMEBREW_PREFIX@@/opt/libftdi0/lib/libftdi.1.dylib" "@executable_path/../Frameworks/libftdi.1.dylib" avrdude
install_name_tool -change "@@HOMEBREW_PREFIX@@/opt/libusb-compat/lib/libusb-0.1.4.dylib" "@executable_path/../Frameworks/libusb-0.1.4.dylib" avrdude

install_name_tool -change "@@HOMEBREW_PREFIX@@/opt/libusb-compat/lib/libusb-0.1.4.dylib" "@executable_path/../Frameworks/libusb-0.1.4.dylib" dfu-programmer

install_name_tool -change "@@HOMEBREW_PREFIX@@/opt/libusb/lib/libusb-1.0.0.dylib" "@executable_path/../Frameworks/libusb-1.0.0.dylib" dfu-util

install_name_tool -id "@executable_path/../Frameworks/libftdi.1.dylib" libftdi.1.dylib
install_name_tool -change "@@HOMEBREW_PREFIX@@/opt/libusb-compat/lib/libusb-0.1.4.dylib" "@executable_path/../Frameworks/libusb-0.1.4.dylib" libftdi.1.dylib

install_name_tool -id "@executable_path/../Frameworks/libusb-1.0.0.dylib" libusb-1.0.0.dylib

install_name_tool -id "@executable_path/../Frameworks/libusb-0.1.4.dylib" libusb-0.1.4.dylib
install_name_tool -change "@@HOMEBREW_PREFIX@@/opt/libusb/lib/libusb-1.0.0.dylib" "@executable_path/../Frameworks/libusb-1.0.0.dylib" libusb-0.1.4.dylib

Suggestions on how to make this process less involved (a script, maybe?) much appreciated.

Types of Changes

  • Core
  • Bugfix
  • New feature
  • Enhancement/optimization
  • Documentation

Issues Fixed or Closed by This PR

@fauxpark
Copy link
Member Author

Turns out, trying to use Mojave bottles on High Sierra is what's causing the "no devices present" errors in dfu-programmer. I switched everything (again...) to the HS bottles instead, hopefully that is low enough.

@drashna drashna merged commit 86b331a into qmk:master Aug 26, 2019
@fauxpark fauxpark deleted the traceable-binaries branch August 26, 2019 22:49
@fauxpark fauxpark mentioned this pull request Jun 13, 2020
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants