No subject
From: ()
Date: Mon Dec 3 19:58:15 EST 2012 |
|
(require compiler/compiler)
(compile-collection-zos "a")
it will try to recompile the whole Racket tree (but fails because it
doesn't have permission to create the directory "compiled/drracket")
It is strange, because I think it did not have this behavior in some
earlier version (maybe 5.3.1?).
So, question: Is there a programmatic equivalent to raco setup for
collections, that won't try to recompile all of Racket?
Laurent
--047d7bfceb18e1c40104d5dace5a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div><div><div><div><div><div><div>Hi,<br><br></div>I=
tried `compile-collection-zos' as a programmatic equivalent to raco se=
tup on a given lib, but it seems there are some differences.<br><br></div>
In particular, if PLTCOMPILEDROOTS is set, raco setup recompiles only the s=
pecified lib, but `compile-collection-zos' tries to recompile all of Ra=
cket.<br><br></div>For example, say I have a personal collection "a&qu=
ot;.<br>
</div>From within DrRacket, if I do:<br></div><div>(require compiler/compil=
er)<br></div>(compile-collection-zos "a")<br></div>it will try to=
recompile the whole Racket tree (but fails because it doesn't have per=
mission to create the directory "compiled/drracket")<br>
<br></div><div>It is strange, because I think it did not have this behavior=
in some earlier version (maybe 5.3.1?).<br></div><div><br></div>So, questi=
on: Is there a programmatic equivalent to raco setup for collections, that =
won't try to recompile all of Racket?<br>
<br></div>Laurent<br><div><div><div><div><div><div><div><div><div><div><div=
><br></div></div></div></div></div></div></div></div></div></div></div></di=
v>
--047d7bfceb18e1c40104d5dace5a--