arrayfire / arrayfire/arrayfire-rust
Statically linking arrayfire
- 主要語言
- Rust
- 星號
- 827
- 分支
- 59
- PR 合併指標
- 30 天內沒有已合併 PR
描述
Right now arrayfire has to be used by linking to the DLL. Since the only parts of arrayfire that are included in the Rust bindings are BSD 3-clause, there should be no problem statically linking arrayfire. Is it possible that we could choose whether or not arrayfire is statically linked to ease distribution? Also, is there any downside to just always statically linking arrayfire? I feel like that would be more in-line with what the Rust community expects: adding a crate to your `Cargo.toml` should "just work".
貢獻指南
這個儲存庫沒有索引到貢獻指南
研究方向
從 Cargo.toml 整合與目前以 DLL 為基礎的 ArrayFire 連結設定開始。調查 Rust bindings 如何選擇與分發 native library,包括可選連結與一律靜態連結之間的取捨。當支援的連結選項及其分發影響已完成文件化並實作,或已明確界定範圍時,即視為完成。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- rust
- 領域
- hpc
- Issue 類型
- 功能
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 25/100