Haddock version during build

[Simon Marlow]

Manuel M T Chakravarty wrote:
> Simon Peyton-Jones:
>> Further to Simon's remarks below:
>>
>> a) Haddock takes a flag telling it where to find its libraries. This 
>> is a pain for users, especially since Haddock is now very fussy about 
>> which libraries it'll understand.
>>
>> So we should somehow arrange that you can tell Haddock where to find 
>> its libraries at install time, so that users don't need to know.
> 
> I don't think that will work.  How will a Linux package manager (rpm, 
> yum, apt, etc) or Mac installer get that path?

I presume you're worried about GHC on the target machine being installed in 
a different place than it was on the build machine?

One plan is to arrange that at install time we generate a script wrapper 
that passes the appropriate path as a flag, similar to the way a GHC binary 
distribution works.

Cheers,
	Simon


> Manuel
> 
>> | -----Original Message-----
>> | From: cvs-libraries-bounces at haskell.org 
>> [mailto:cvs-libraries-bounces at haskell.org] On Behalf Of Simon
>> | Marlow
>> | Sent: 04 June 2008 14:20
>> | To: David Waern; Duncan Coutts; cvs-libraries at haskell.org; Manuel M 
>> T Chakravarty
>> | Subject: Re: Haddock version during build
>> |
>> | So Simon PJ and I just discussed this, and we have a rough plan.
>> |
>> | The basic problem is that in order to build documentation for the 
>> libraries
>> | in a GHC build tree using Haddock 2, we have to build Haddock 2 
>> using the
>> | stage2 GHC.  There's no alternative, because when running Haddock 
>> against
>> | one of the packages in the build tree, it needs to read the 
>> interface files
>> | for the other packages.
>> |
>> | So the rough plan is this: if we need to build documentation during a
>> | build, then we check out a copy of Haddock into the build tree (it's 
>> still
>> | a separate repository, like the libraries), and we build Haddock after
>> | stage 2, before generating the documentation.  We don't have to ship 
>> this
>> | Haddock with GHC, it's just a temporary build tool.
>> |
>> | Sound reasonable?
>> |
>> | Cheers,
>> |         Simon
>> |
>> | _______________________________________________
>> | Cvs-libraries mailing list
>> | Cvs-libraries at haskell.org
>> | http://www.haskell.org/mailman/listinfo/cvs-libraries
>> _______________________________________________
>> Cvs-libraries mailing list
>> Cvs-libraries at haskell.org
>> http://www.haskell.org/mailman/listinfo/cvs-libraries
>