In message <[EMAIL PROTECTED]>
alan buckley <[EMAIL PROTECTED]> wrote:
>
> I was wondering if it would make sense to modify the !SharedLibs
> !Boot file so that it could automatically load the SO Manager
> when an ELF file was run.
>
> I was thinking of changing the boot entry for ELF files to:
>
> Set [EMAIL PROTECTED] SharedLibs:SOM1stRun %%*0
>
> and have a new Obey file in the SharedLibs folder called
> SOM1stRun with the following contents.
>
> | Load the SOManager and run an ELF executable
>
> RMEnsure SOManager 2.00 RMLoad SharedLibs:SOManager
> RMEnsure SOManager 2.00 Error Need at least v2.00 of Shared Object Manager
> (SOManager)
>
> Set [EMAIL PROTECTED] SOMRun %%*0
>
> SOMRun %*0
>
> Any comments?
Yes, I don't think this is a good idea. Why would you do that instead of
only relying on activation when !SharedLibs gets run ?
Loading a module when Filer sees a directory is bound to have user
dissatisfaction IMHO. Firstly just by the fact binaries get automatically
loaded. And secondly, you could have a Wimp_ReportError error with the
RMEnsured lines mentioned above [1].
I see a suitable place for !SharedLibs in the system's !Boot.Resources
as all those apps get automatically run at boot time and SOManager will be
loaded at that moment. And we could even finetune its current !Run so that
SOManager module only gets loaded when the first ELF binary is executed.
John.
[1] Suppose we issue SOManager v2.1 which has in its !Boot file an RMEnsure
2.10 and the user has SOManager v2.00 loaded already containing active
shared libs in memory; SOManager v2.00 will refuse to die and this results
in a Wimp_ReportError box on opening a Filer window...
--
John Tytgat, in his comfy chair at home BASS
[EMAIL PROTECTED] ARM powered, RISC OS driven
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
