Hi,
On Mon, Jan 20, 2014 at 11:50 AM, Simon Marlow wrote:
>
> There is nothing fundamental about -split-objs that prevents it from working
> with executables. I expect that GHC doesn't take it into account during its
> link step when linking an executable with -split-objs, though. That would
>
On 19/12/2013 03:00, Mikhail Glushenkov wrote:
The problem in https://github.com/haskell/cabal/issues/1611 is with
that we have a module (say, A) from which we're only importing a
single value, and this module is a part of the cabal-install source
tree. It would be nice if the whole contents of A
Hi,
The problem in https://github.com/haskell/cabal/issues/1611 is with
that we have a module (say, A) from which we're only importing a
single value, and this module is a part of the cabal-install source
tree. It would be nice if the whole contents of A weren't linked with
the final executable. S
On Wed, Dec 18, 2013 at 10:27 AM, harry wrote:
> Brandon Allbery wrote
> > I don't understand the question. Whether a library is split-objs or not
> > does not affect how you link an executable, only the space/time
> efficiency
> > trade-off of doing so. And while in theory you might see improvem
Brandon Allbery wrote
> I don't understand the question. Whether a library is split-objs or not
> does not affect how you link an executable, only the space/time efficiency
> trade-off of doing so. And while in theory you might see improvements by
> split-objs-ing an executable, it doesn't make a w
On Wed, Dec 18, 2013 at 4:08 AM, harry wrote:
> The documentation for --split-objs states that "this only makes sense for
> libraries". How is an executable compiled against a split-objs library?
> According to
> https://github.com/haskell/cabal/issues/1611#issuecomment-30750655, this
> isn't hap
On 29 July 2005 05:10, Dimitry Golubovsky wrote:
> Is it possible to use --make when one or more of modules involved are
> split?
Not right now, but it's on the ToDo list.
Cheers,
Simon
___
Glasgow-haskell-users mailing list
Glasgow-haskell-us
