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
It's common for cmake files to detect the presence of existing libraries and change the behavior accordingly. How do we ensure / improve hermeticity in this case when using cmake rules? E.g. my build rules work on one device, but fail on another due to some libraries only existing on one of them and cmake build result differing.
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
-
It's common for cmake files to detect the presence of existing libraries and change the behavior accordingly. How do we ensure / improve hermeticity in this case when using cmake rules? E.g. my build rules work on one device, but fail on another due to some libraries only existing on one of them and cmake build result differing.
Any best practice for this? Thanks very much!
Beta Was this translation helpful? Give feedback.
All reactions