[racket] runtime-path + dynamic-require ?

DrRacket does not, that's right. I think you'd have to do something to
tell your distribution packer about the dynamically required files
from the outside, I'm sorry to say.

AT least I don't see a better way, but maybe others do.

Robby

On Fri, Sep 10, 2010 at 10:41 AM, Laurent <laurent.orseau at gmail.com> wrote:
>
>
> On Fri, Sep 10, 2010 at 17:38, Robby Findler <robby at eecs.northwestern.edu>
> wrote:
>>
>> On Fri, Sep 10, 2010 at 10:18 AM, Laurent <laurent.orseau at gmail.com>
>> wrote:
>> >
>> >
>> > On Fri, Sep 10, 2010 at 17:06, Laurent <laurent.orseau at gmail.com> wrote:
>> >>
>> >>
>> >> On Fri, Sep 10, 2010 at 16:43, Sam Tobin-Hochstadt <samth at ccs.neu.edu>
>> >> wrote:
>> >>>
>> >>> On Fri, Sep 10, 2010 at 10:34 AM, Laurent <laurent.orseau at gmail.com>
>> >>> wrote:
>> >>> >
>> >>> > So now, how do I make things work with `dynamic-require' ?
>> >>> > Do all paths need to be defined as runtime-paths in my "splash.rkt",
>> >>> > to use only normal relative paths in dynamically required files?
>> >>> > Or can I get completely rid of runtime-path?
>> >>>
>> >>> I believe that you should add:
>> >>>
>> >>> (define-runtime-module-path name require-path)
>> >>>
>> >
>> > One caveat though:  since such modules sub-dependencies are not "files"
>> > anymore,
>> > framework/splash won't recognize them, and then gauge in the
>> > splashscreen
>> > will not
>> > animate smoothly but will be binary.
>>
>> I think the splash doesn't animate anymore because the files are
>> already loaded by define-runtime-module-path.
>>
>
> Is there a way around this?
>
> Or does this mean DrRacket does not use define-runtime-module-path?
>
>
>