You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i don't know 1000% that this is safe, but we did it at one point with limited consequence, if i recall. libtool archives (.la) are static text files, which don't provide any functionality akin to pkg-config's ${pcfiledir} expansion. add to that the fact that the the +brewing suffix commonly ends up in them, they require hacky treatment to work in our environment, and are completely broken for anyone not installing to /opt.
i am not certain that every build processes will work without libtool archives, however. i believe they fall back to include paths, pkg-config, and other options, but it's hard to be certain.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
i don't know 1000% that this is safe, but we did it at one point with limited consequence, if i recall. libtool archives (
.la
) are static text files, which don't provide any functionality akin topkg-config
's${pcfiledir}
expansion. add to that the fact that the the+brewing
suffix commonly ends up in them, they require hacky treatment to work in our environment, and are completely broken for anyone not installing to/opt
.i am not certain that every build processes will work without libtool archives, however. i believe they fall back to include paths, pkg-config, and other options, but it's hard to be certain.
Beta Was this translation helpful? Give feedback.
All reactions