Checking use of UnixLib
Chris Hall (132) 3505 posts |
UnixLib is a library that NetSurf (and most software built with GCCSDK) are statically linked against. The library used the SWP instruction, not supported on latest hardware. Although the SharedUnixLib is something different, is a check whether an application’s !Boot or !Run files RMEnsure SharedUnixLib a sufficient check to determine whether the application was built with GCCSDK and was statically linked against UnixLib? |
Chris Hall (132) 3505 posts |
Answering (part of) my own question, I am told that I also need to examine any application file or module file in the same directory as the !Run file (using ‘xpand’ on an Application file and ‘unmodsqz’ on a Module file to make sure they are not squeezed) for the word ‘Unix’. This gives a positive for
as well as Netsurf (which gives positives both ways). |
Alan Buckley (167) 232 posts |
Chris, UnixLib itself will RMEnsure the SharedUnixLibrary so a RMEnsure in !Boot or !Run is not necessary. This means an absence of the RMEnsure doesn’t mean it’s not a UnixLib program. |
Chris Hall (132) 3505 posts |
This means an absence of the RMEnsure doesn’t mean it’s not a UnixLib program. Ah! That explains why the lack of RMEnsure in Boot or Run is not diagnostic. Hence the search (using !Zap) of the executable to look for RMEnsure (via a search for ‘Unix’ which actually found SWI SharedUnixLibrary_Initialise). The question now is whether that wider test (described) is now sufficient… |