haskell/cabal

`executable-dynamic: True` should apply to `build-type: Custom` setup

Open

#1,720 建立於 2014年3月10日

在 GitHub 查看
 (6 留言) (3 反應) (0 負責人)Haskell (1,731 star) (732 fork)batch import
Cabal: file formatCabal: otherattention: pr-welcomegood first issuetype: enhancement

描述

I have a Haskell installation with only shared libraries, and cabal's config contains:

library-vanilla: False
library-profiling: False
shared: True
executable-dynamic: True

This fails for packages with build-type: Custom, because cabal-install tries to link setup against non-existent static libraries.

貢獻者指南

技術棧
無
領域
build systemtooling
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic knowledge of cabalUnderstanding of static vs shared libraries in Haskell
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
25
研究方向
The issue describes a bug where `executable dynamic: True` is not applied to packages with `build type: Custom`, causing linking failures against absent static libraries. Investigate how cabal install selects linking flags for the setup executable, likely in `Distribution.Simple.Build`. Look for any existing comments or proposed solutions in the discussion. The fix may involve modifying the build system to propagate the dynamic linking setting to the setup executable.