Subversion Repositories Kolibri OS

Rev

Rev 5568 | Show entire file | Regard whitespace | Details | Blame | Last modification | View Log | RSS feed

Rev 5568 Rev 9583
Line 248... Line 248...
248
    and want to test changes.
248
    and want to test changes.
249
A7. First, you need to build the corresponding binary as described in Q1/A1 or
249
A7. First, you need to build the corresponding binary as described in Q1/A1 or
250
    Q2/A2.
250
    Q2/A2.
251
    To test a program, it is sufficient to put it to some place accessible
251
    To test a program, it is sufficient to put it to some place accessible
252
    to the working KolibriOS and just run it from there. Drivers are loaded
252
    to the working KolibriOS and just run it from there. Drivers are loaded
253
    from the folder /rd/1/drivers/, which is initialized from kolibri.img,
253
    from the folder /rd/1/drivers, which is initialized from kolibri.img,
254
    so testing a driver requires either copying the compiled binary to
254
    so testing a driver requires either copying the compiled binary to
255
    /rd/1/drivers manually between KolibriOS startup and loading driver or
255
    /rd/1/drivers manually between KolibriOS startup and loading driver or
256
    inserting the driver to the image kolibri.img outside of KolibriOS.
256
    inserting the driver to the image kolibri.img outside of KolibriOS.
257
    Testing the kernel or an auto-loading driver requires modifying the image.
257
    Testing the kernel or an auto-loading driver requires modifying the image.