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
Can't use a native library from the user's PATH with Fake 5.14+.
Repro steps
Use functionality (whether from a Nuget package or written directly into a script) which relies on a native library being in the PATH environment variable rather than a Nuget package. For example:
Build 00:00:00.0056542 (Could not resolve native library 'kernel32.dll'. No native libraries found!
This can happen for various reasons:
- The nuget cache (or packages folder) might be broken.
-> Please save your state, open an issue and then
- delete the source package of 'kernel32.dll' from the '~/.nuget' cache (and the 'packages' folder)
- delete 'paket-files/paket.restore.cached' if it exists
- delete '<script.fsx>.lock' if it exists
- try running fake again
- the package should be downloaded again
-> If the above doesn't apply or you need help please open an issue!)
Known workarounds
Use Fake v 5.13.7
Related information
Operating system - Windows 10
Version of FAKE - > 5.14
The text was updated successfully, but these errors were encountered:
Ah indeed, didn't realize that FAKE already supported this. Shouldn't be too hard to add this. Question is if we can properly detect this case and report the above error otherwise.
Description
Can't use a native library from the user's
PATH
with Fake 5.14+.Repro steps
PATH
environment variable rather than a Nuget package. For example:There's a small repository demonstrating the issue at https://github.com/BillHally/FakeNativeLibraryIssue.
Expected behavior
Functionality works
Actual behavior
An exception is raised. For example:
Known workarounds
Use Fake v 5.13.7
Related information
The text was updated successfully, but these errors were encountered: