[racket-dev] building docs, compile collects

From: Robby Findler (robby at eecs.northwestern.edu)
Date: Mon Oct 25 16:59:39 EDT 2010

I think CM already does this, no (that's how drracket builds zo files
for you, for example)? So it needs to be packaged up a little bit,
perhaps, for some settings in your .racket file?

You might look at how the PLTDRCM environment variable is implemented,
if the docs aren't helpful enough.


On Mon, Oct 25, 2010 at 3:54 PM, Jon Rafkind <rafkind at cs.utah.edu> wrote:
> I would like on-demand compilation of the collects tree. It seems there
> are two reasons why it doesn't exist right now
> 1. building the documentation requires the collects tree to be touched,
> so its worthwhile to just compile everything in there
> 2. users might not have write access to the collects tree
> I use docs.racket-lang.org almost exclusively (because its simpler for
> me to open) so I'm not too concerned with 1. There are rare times when I
> need local docs and in those cases I don't mind building all of
> collects. And as a developer 2. is not much of a concern.
> I imagine some configure switch would allow the compilation manager to
> assume write access to the collects tree thus solving issue 2 and a new
> `make' install target that only copies the binaries to bin/ would solve 1.
> My motivation is to quickly test changes to core libraries (like
> collects/racket) after doing a 'git pull --rebase'.
> How hard would something like this be?
> _________________________________________________
>  For list-related administrative tasks:
>  http://lists.racket-lang.org/listinfo/dev

Posted on the dev mailing list.