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
If you create a foreign-library stanza with type: native-shared and a lib-version-info field, cabal will create a library with a version number in its name, but tell you about a non-existent unversioned name. Typical example, with both commands executed after running cabal build all:
Two plausible solutions are to change list-bin (to include the version number in the reported file name) or to change build (to create an unversioned link to the versioned file); I don't really know enough to be clear on the tradeoffs between them.
The text was updated successfully, but these errors were encountered:
If you create a
foreign-library
stanza withtype: native-shared
and alib-version-info
field, cabal will create a library with a version number in its name, but tell you about a non-existent unversioned name. Typical example, with both commands executed after runningcabal build all
:Two plausible solutions are to change
list-bin
(to include the version number in the reported file name) or to changebuild
(to create an unversioned link to the versioned file); I don't really know enough to be clear on the tradeoffs between them.The text was updated successfully, but these errors were encountered: