-
Notifications
You must be signed in to change notification settings - Fork 18
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
add toolchain shims here #175
Conversation
* only added if no other toolchain is added * on linux shim through to llvm * on mac shim through to system rationale * reduces hacks in our infra * these are only used with pantry builds * brewkit controls that * everyone expects a C compiler, builds either will work with this or they need to be more specifiuc * for end users removes the surprise of `cc` being some weird hack * end users have to control rpaths themselves and if they are going that low-level then they know what to do * magic is bad
while I think this is the right approach I note that Thus the above approach is not adequate, instead we will need to dynamically create symlinks on linux that point to the installed llvm. I'll consider whether this is sensible in advance of v1.0 next week. I'm thinking: no: there are too many moving parts already. |
the failure is fixed in tea/cli v1 |
* add toolchain shims here * only added if no other toolchain is added * on linux shim through to llvm * on mac shim through to system rationale * reduces hacks in our infra * these are only used with pantry builds * brewkit controls that * everyone expects a C compiler, builds either will work with this or they need to be more specifiuc * for end users removes the surprise of `cc` being some weird hack * end users have to control rpaths themselves and if they are going that low-level then they know what to do * magic is bad
rationale
cc
being some weird hack