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 would be very useful to have the ability to use multiple sources in a [wrap-file] section.
When wrapping binary only libraries its not uncommon that a single redistributable zip contains only one platforms binaries in a single zip which requires unpleasant build logic and wrap layout to handle building on multiple platforms - e.g. dxc-windows + dxc-linux + build logic for providing dxc on both windows and linux with associated build logic to pick the correct one.
It's also a common case that headers and shared objects are distributed separately - e.g. the linux oracledb instantclient SDK headers and runtime shared objects are distributed in separate zip files - link.
Alot of the time these files aren't legally redistributable by a third party, which makes merging these zips together and providing them yourself legally grey. It would be nice to be able to specify multiple source files, and to be able to select a wrap file to download based on host_machine.system(), host_machine.cpu_family().
Are there any plans to improve wrap files already in progress or would an example implementation be worthwhile?
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 would be very useful to have the ability to use multiple sources in a
[wrap-file]
section.When wrapping binary only libraries its not uncommon that a single redistributable zip contains only one platforms binaries in a single zip which requires unpleasant build logic and wrap layout to handle building on multiple platforms - e.g. dxc-windows + dxc-linux + build logic for providing dxc on both windows and linux with associated build logic to pick the correct one.
It's also a common case that headers and shared objects are distributed separately - e.g. the linux oracledb instantclient SDK headers and runtime shared objects are distributed in separate zip files - link.
Alot of the time these files aren't legally redistributable by a third party, which makes merging these zips together and providing them yourself legally grey. It would be nice to be able to specify multiple source files, and to be able to select a wrap file to download based on
host_machine.system()
,host_machine.cpu_family()
.Are there any plans to improve wrap files already in progress or would an example implementation be worthwhile?
Beta Was this translation helpful? Give feedback.
All reactions