How to build statically linking GHC?
What's the correct way, on GHC head, to get it to build libraries in the way GHC does now (so that they are statically linked into binaries) instead of the new-but-super-annoying dynamic linking? Do I just DYNAMIC_BY_DEFAULT=NO in my build.mk? -- Stephen Paul Weber, @singpolyma See http://singpolyma.net for how I prefer to be contacted edition right joseph
Interesting. Why "super-annoying"? Simon | -----Original Message----- | From: ghc-devs-bounces@haskell.org [mailto:ghc-devs-bounces@haskell.org] | On Behalf Of Stephen Paul Weber | Sent: 16 June 2013 21:05 | To: ghc-devs@haskell.org | Subject: How to build statically linking GHC? | | What's the correct way, on GHC head, to get it to build libraries in the | way | GHC does now (so that they are statically linked into binaries) instead | of | the new-but-super-annoying dynamic linking? Do I just | DYNAMIC_BY_DEFAULT=NO | in my build.mk? | | -- | Stephen Paul Weber, @singpolyma | See http://singpolyma.net for how I prefer to be contacted | edition right joseph | | _______________________________________________ | ghc-devs mailing list | ghc-devs@haskell.org | http://www.haskell.org/mailman/listinfo/ghc-devs
Somebody claiming to be Simon Peyton-Jones wrote:
Interesting. Why "super-annoying"?
Because I have to find and copy many files and then set up the library path env vars when distributing. Especially since the average Haskell project relies on *many* libraries, this gets crazy fast. Distributing to sane systems like Debian (where I could just set dependencies) would be fine, but for, say, blackberry app dev or windows or mac, it just gets in the way. In fact, the static haskell librarie, dynamic C libraries approach GHC took was a major selling point when my company was choosing what platform to target for our blackberry development. -- Stephen Paul Weber, @singpolyma See http://singpolyma.net for how I prefer to be contacted edition right joseph
On Mon, Jun 17, 2013 at 12:12:55PM +0000, Stephen Paul Weber wrote:
Because I have to find and copy many files and then set up the library path env vars when distributing. Especially since the average Haskell project relies on *many* libraries, this gets crazy fast.
I'm a little confused. GHC still builds static programs by default. (well, statically-linked Haskell, dynamically-linked to C libs, like before). Thanks Ian -- Ian Lynagh, Haskell Consultant Well-Typed LLP, http://www.well-typed.com/
participants (3)
-
Ian Lynagh -
Simon Peyton-Jones -
Stephen Paul Weber