Support native DLLs in generate-load-scripts
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
Related to https://github.com/dotnet/machinelearning/issues/92#issuecomment-390937877. Some .NET Nuget packages (CosmosDB in another culprit) bundle (and use) OS-specific native DLLs in their packages.
Paket's generate-load-scripts functionality correctly does #load and #r for all .NET packages assemblies, but doesn't currently support native DLLs. Unlike .NET assemblies, you need to add the native package folder to the path e.g.
let nativeDirectory = @"C:\Users\Isaac\.nuget\packages\microsoft.ml\0.1.0\runtimes\win-x64\native"
Environment.SetEnvironmentVariable("Path", Environment.GetEnvironmentVariable("Path") + ";" + nativeDirectory)
This is something with should be possible to achieve in Paket.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at Paket's generate-load-scripts functionality and inspect how it currently emits #load and #r entries for NuGet assemblies. Done means generated scripts also make OS-specific native package directories available on PATH, including the Microsoft.ML or CosmosDB cases described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100