<br><br><div class="gmail_quote">On Fri, Sep 10, 2010 at 17:06, Laurent <span dir="ltr"><<a href="mailto:laurent.orseau@gmail.com">laurent.orseau@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <br><br><div class="gmail_quote"><div><div></div><div class="h5">On Fri, Sep 10, 2010 at 16:43, Sam Tobin-Hochstadt <span dir="ltr"><<a href="mailto:samth@ccs.neu.edu" target="_blank">samth@ccs.neu.edu</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <div>On Fri, Sep 10, 2010 at 10:34 AM, Laurent <<a href="mailto:laurent.orseau@gmail.com" target="_blank">laurent.orseau@gmail.com</a>> wrote:<br> ><br> > So now, how do I make things work with `dynamic-require' ?<br> > Do all paths need to be defined as runtime-paths in my "splash.rkt",<br> > to use only normal relative paths in dynamically required files?<br> > Or can I get completely rid of runtime-path?<br> <br> </div>I believe that you should add:<br> <br> (define-runtime-module-path name require-path)<br><br></blockquote></div></div></div></blockquote><div><br>One caveat though: since such modules sub-dependencies are not "files" anymore, <br>framework/splash won't recognize them, and then gauge in the splashscreen will not<br> animate smoothly but will be binary.<br></div></div>