Setting (or not) DYLD_LIBRARY_PATH #1737
-
I work on QMK Firmware, a pretty popular firmware for custom mechanical keyboards. We have some users who are starting to run into issues on their M1 macs, but as none of the maintainers have one we have limited ability to work on this ourselves. We recommend users install with rosetta which still works fine, but some users still try to use the AS native version, which has one issue in particular that's proving troublesome- the need to set Trying to summarize as much as possible, here is my understanding of the situation:
The problem that we (QMK Firmware) face is what to do here. We can figure out how to ensure that * Everytime I write ISTM you can mentally replace it with "I'm making a big assumption here and am probably wrong." |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
I commented at qmk/qmk_cli#60 to see if there are fixes we can apply in Homebrew. |
Beta Was this translation helpful? Give feedback.
-
Homebrew/homebrew-core#80052 should fix this. |
Beta Was this translation helpful? Give feedback.
make
doesn't wipe outDYLD_LIBRARY_PATH
, Apple's System Integrity Protection does. I believe the rule is that it doesn't propagate into subshells, but I don't think that's something we can rely on. Setting it also tends to break things. You really don't want your build to depend on being able to set this variable.I commented at qmk/qmk_cli#60 to see if there are fixes we can apply in Homebrew.