[racket] raco setup and compile-collection-zos

On Wed, Feb 20, 2013 at 3:06 PM, Matthew Flatt <mflatt at cs.utah.edu> wrote:

> The problem is that DrRacket sets various other parameters that affect
> compilation --- so that the programs you run within DrRacket get
> automatically compiled, for example.
>
> It's possible that things used to work back before `Populate "compiled"
> directories' was on by default in DrRacket, and turning off that option
> in the language dialog may make things work for you.
>

Actually, I'm not really bothered by DrRacket here.
I'd like to be able to compile a collection from command line racket code,
without triggering compilation of the Racket's collections when
PLTCOMPILEDROOT is modified.



> More generally, I don't think we've figured out the right way to make
> different compilation and debugging systems stay out of each others'
> way.
>

Ah, that's too bad.
At the very least, I can call the compilation within a system call, but
that's quite ugly.
Plus "raco setup my-collec" used to have the same problematic behavior as
described above (recompilation of Racket's collections) on some occasions,
although I think I haven't seen it during the last 2 weeks.

Laurent
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/users/archive/attachments/20130220/9089742c/attachment.html>