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
At present, it is assumed that a dependency may only be included once for an entire build, which does not allow for using different versions of a dependency in a chain.
A related issue, there is no way to indicate that two dependencies will conflict if both loaded into the same process.
Add capability for recipes to have "static" dependencies.
Static dependencies would be built in addition to normal (shared) dependencies, meaning that two recipes in a dependency chain could depend on different versions and from different cookbooks of the same library without conflicting.
For compiled and linked software, any recipe which uses a static dependency must use a recipe that builds a static library and it must statically link the the static library.
Recipes could be able to provide "incompatible_with" (or some similar verbiage) lists to indicate other libraries that will cause a conflict, unless the recipe is static. Example incompatibility: libjson-c must not be included with libjson-gnu or jansson, unless all but one (or all) are static. This feature would help people avoid symbol collisions that will cause crashes during runtime.
The text was updated successfully, but these errors were encountered:
At present, it is assumed that a dependency may only be included once for an entire build, which does not allow for using different versions of a dependency in a chain.
A related issue, there is no way to indicate that two dependencies will conflict if both loaded into the same process.
The text was updated successfully, but these errors were encountered: