Building the Software on an Acorn RISC OS systemThe directory contrib/acorn contains support for compiling the library underAcorn C/C++ under Acorn's RISC OS 3.10 or above. Subsequent pathnames willuse the Acorn format: The full-stop or period character is a pathnamedelimeter, and the slash character is not interpreted; the reverse positionfrom Unix. Thus "libtiff/tif_acorn.c" becomes "libtiff.tif_acorn/c".This support was contributed by Peter Greenham.(peterg@angmulti.demon.co.uk).Installing LibTIFF:LIBTIFF uses several files which have names longer than the normal RISC OSmaximum of ten characters. This complicates matters. Maybe one day Acorn willaddress the problem and implement long filenames properly. Until then thisgets messy, especially as I'm trying to do this with obeyfiles and not haveto include binaries in this distribution.First of all, ensure you have Truncate configured on (type *ConfigureTruncate On) Although it is, of course, preferable to have long filenames,LIBTIFF can be installed with short filenames, and it will compile and linkwithout problems. However, getting it there is more problematic.contrib.acorn.install is an installation obeyfile which will create a normalAcorn-style library from the source (ie: with c, h and o folders etc.), butneeds the distribution library to have been unpacked into a location which iscapable of supporting long filenames, even if only temporarily.My recommendation, until Acorn address this problem properly, is to use JasonTribbeck's LongFilenames , or any other working system that gives you longfilenames, like a nearby NFS server for instance.If you are using Longfilenames, even if only temporarily to install LIBTIFF,unpack the TAR into a RAMDisc which has been longfilenamed (ie: *addlongfsram) and then install from there to the hard disk. UnfortunatelyLongfilenames seems a bit unhappy about copying a bunch of long-named filesacross the same filing system, but is happy going between systems. You'llneed to create a ramdisk of about 2Mb.Now you can run the installation script I've supplied (in contrib.acorn),which will automate the process of installing LIBTIFF as an Acorn-stylelibrary. The syntax is as follows:install <source_dir> <dest_dir>Install will then create <dest_dir> and put the library in there. Forexample, having used LongFilenames on the RAMDisk and unpacked the libraryinto there, you can then type:Obey RAM::RamDisc0.$.contrib.acorn.install RAM::RamDisc0.$ ADFS::4.$.LIBTIFFIt doesn't matter if the destination location can cope with long filenames ornot. The filenames will be truncated if necessary (*Configure Truncate On ifyou get errors) and all will be well.Compiling LibTIFF:Once the LibTIFF folder has been created and the files put inside, making thelibrary should be just a matter of running 'SetVars' to set the appropriatesystem variables, then running 'Makefile'.OSLibOSLib is a comprehensive API for RISC OS machines, written by JonathanCoxhead of Acorn Computers (although OSLib is not an official Acorn product).Using the OSLib SWI veneers produces code which is more compact and moreefficient than code written using _kernel_swi or _swi. The Acorn port ofLibTIFF can take advantage of this if present. Edit the Makefile and go tothe Static dependencies section. The first entry is:# Static dependencies:@.o.tif_acorn:   @.c.tif_acorn        cc $(ccflags) -o @.o.tif_acorn @.c.tif_acorn  Change the cc line to:        cc $(ccflags) -DINCLUDE_OSLIB -o @.o.tif_acorn @.c.tif_acorn  Remember, however, that OSLib is only recommended for efficiency's sake. Itis not required.