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
There are some builds (mostly cmake-based) that accept a prefix path to static and shared libraries $prefix/lib and $prefix/include. This becomes a problem when the derivation puts includes and static libraries into separate outputs, so that there is no such common prefix. To work around this, we end up needing to patch the build scripts, which is a burden. I was wondering if there can be a general solution to this. I propose creating a wrapper derivation that would instantiate into a path with symlinks to all outputs:
There are some builds (mostly cmake-based) that accept a prefix path to static and shared libraries $prefix/lib and $prefix/include. This becomes a problem when the derivation puts includes and static libraries into separate outputs, so that there is no such common prefix. To work around this, we end up needing to patch the build scripts, which is a burden. I was wondering if there can be a general solution to this. I propose creating a wrapper derivation that would instantiate into a path with symlinks to all outputs:
For example if
foo
instantiates to:and
foo.dev
instantiates to:Then proposed
symlink_combine [foo foo.dev]
would instantiate to something like:The text was updated successfully, but these errors were encountered: