<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 20, 2013 at 3:06 PM, Matthew Flatt <span dir="ltr"><<a href="mailto:mflatt@cs.utah.edu" target="_blank">mflatt@cs.utah.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The problem is that DrRacket sets various other parameters that affect<br>
compilation --- so that the programs you run within DrRacket get<br>
automatically compiled, for example.<br>
<br>
It's possible that things used to work back before `Populate "compiled"<br>
directories' was on by default in DrRacket, and turning off that option<br>
in the language dialog may make things work for you.<br></blockquote><div><br></div><div>Actually, I'm not really bothered by DrRacket here.<br></div><div>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.<br>
<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
More generally, I don't think we've figured out the right way to make<br>
different compilation and debugging systems stay out of each others'<br>
way.<br></blockquote><div><br></div><div>Ah, that's too bad. <br></div><div>At the very least, I can call the compilation within a system call, but that's quite ugly.<br></div><div>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.<br>
<br></div><div>Laurent<br></div></div></div></div>