OSLib 6.11 Released

[Jonathan Coxhead]

   On 26 Sep 00, Stewart Brodie wrote,
 
 | If you want to avoid using the path in the #include statements, then you
 | should fallback to requiring people to use multiple -I arguments to the
 | compiler.  This is the way it works on other platforms!

   It doesn't help, though. If you have 2 files called "wimp.h" (in 
OSLib:User and RISC_OSLib:, say), and you use

      cc -IOSLib:User -IRISC_OSLib:

you have no way to tell them apart.

   The solution with a "/" in the #include line (either "oslib/wimp.h" or 
"User/wimp.h") does let you do

      cc -IOSLib: -IRISC_OSLib:

and either

      #include "oslib/wimp.h" //or "User/wimp.h"

(for the OSLib one) or

      #include "wimp.h"

(for the RISC_OSLib one) and everything works smoothly.

 | Alternatively, you
 | could have RISC OS-specific install targets that do the multiple directory
 | stuff, and non-RISC OS targets that shove everything into a single directory.
 | 
 | One possibility that would probably suit only me personally would be to
 | commit to a specific release of OSLib and simply rearrange it all by hand and
 | never use a later version.  In effect, that is the current position here -
 | we're using OSLib 4.something and have no need to upgrade as very little of
 | our source code uses OSLib.

   That's always a solution---but if the library can help the users by 
doing commonly-useful things for them, there's no reason it shouldn't.

        /|
 o o o (_|/
        /|
       (_/