Friday, November 8, 2024

terminal – The way to add Google Chrome to path?

The exact error message reveals that it tries to open extra information relative to the binary you launched.

macbook:~ tripleee$ ln -s /Purposes/Google Chrome.app/Contents/MacOS/Google Chrome ~/bin/google-chrome
macbook:~ tripleee$ google-chrome
dlopen /Customers/tripleee/bin/../Frameworks/Google Chrome Framework.framework/Variations/120.0.6099.71/Google Chrome Framework: dlopen(/Customers/tripleee/bin/../Frameworks/Google Chrome Framework.framework/Variations/120.0.6099.71/Google Chrome Framework, 0x0105): tried: '/Customers/tripleee/bin/../Frameworks/Google Chrome Framework.framework/Variations/120.0.6099.71/Google Chrome Framework' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/Customers/tripleee/bin/../Frameworks/Google Chrome Framework.framework/Variations/120.0.6099.71/Google Chrome Framework' (no such file), '/Customers/tripleee/bin/../Frameworks/Google Chrome Framework.framework/Variations/120.0.6099.71/Google Chrome Framework' (no such file).Abort entice: 6

The easy and apparent workaround is to make a wrapper script which calls the actual binary at its authentic location as an alternative, with out the --headless choice.

#!/bin/sh
exec "/Purposes/Google Chrome.app/Contents/MacOS/Google Chrome" "$@"

Save as /usr/native/bin/google-chrome (or wherever you need it), chmod a+x, and go.

Want /bin/sh over /bin/bash as it’s considerably smaller, and use exec to keep away from having the shell dangle round ready for Chrome when it is not going to do something extra after Chrome exits.

Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Latest Articles