| 1 |
Acorn-specific compile instructions |
| 2 |
----------------------------------- |
| 3 |
|
| 4 |
Use the "RunMe1st" file (it is an Obey file) to convert all the files from |
| 5 |
"filename/[chs]" to "[chs].filename" (so that zip could be easily compiled |
| 6 |
under RISC OS). It will also set the correct makefile. |
| 7 |
|
| 8 |
To compile just set the CSD to the main zip directory and run 'amu'. |
| 9 |
|
| 10 |
Currently only the Acorn C V5 compiler has been tested but probably also |
| 11 |
Acorn C V4 and the Acorn Assembler V2 will be able to compile zip. |
| 12 |
|
| 13 |
The default makefile is configured without the support for the |
| 14 |
Extended Timestamp Extra Field. If you wan to enable it you have to |
| 15 |
add "-DUSE_EF_UT_TIME" to CFLAGS (see makefile). Without the Extended |
| 16 |
Timestamp Field support, zipfiles created by zip are identical to the |
| 17 |
zipfiles created by SparkFS. However, the Extended Timestamp Field can |
| 18 |
be useful if you are going to unzip your zipfiles on a non-RISC OS machine |
| 19 |
since the correct time stamp will be preserved across different timezones. |
| 20 |
Note that in this case, both the SparkFS Extra Field and the Extended |
| 21 |
Timestamp Extra Field will be used, so the zipfiles will still be fully |
| 22 |
compatible with SparkFS and with the RISC OS version of unzip. |
| 23 |
|
| 24 |
The executables-only distributions will be compiled without the support for |
| 25 |
the Extended Timestamp Extra Field. If you need it but you can't compile zip |
| 26 |
yourself, you can contact the authors at the Info-ZIP address who will do it |
| 27 |
for you. |
| 28 |
|
| 29 |
|
| 30 |
Acorn-specific usage instructions |
| 31 |
--------------------------------- |
| 32 |
|
| 33 |
An extra option ('I') has been added to the Acorn port: if it is specified |
| 34 |
zip will not consider Image files (eg. DOS partitions or Spark archives when |
| 35 |
SparkFS is loaded) as directories but will store them as single files. This |
| 36 |
means that if you have, say, SparkFS loaded, zipping a Spark archive will |
| 37 |
result in a zipfile containing a directory (and its content) while using the |
| 38 |
'I' option will result in a zipfile containing a Spark archive. Obviously |
| 39 |
this second case will also be obtained (without the 'I' option) if SparkFS |
| 40 |
isn't loaded. |
| 41 |
|
| 42 |
When adding files to a zipfile; to maintain FileCore compliance, all |
| 43 |
files named "file/ext" will be added to the archive as "file.ext". |
| 44 |
This presents no problem if you wish to use unzip to extract them on any |
| 45 |
other machine, as the files are correctly named. This also presents no |
| 46 |
problem if you use unzip for RISC OS, as the files are converted back to |
| 47 |
"file/ext" format. The only problem appears when you use SparkFS to |
| 48 |
decompress the files, as a file called "file.ext" will be extracted as |
| 49 |
"file_ext", not what it was added as. You must be careful about this. |
| 50 |
|
| 51 |
Case Specific. Depending on how you type the command, files will be added |
| 52 |
exactly as named; in this example: |
| 53 |
*zip new/zip newfile |
| 54 |
*zip new/zip NewFile |
| 55 |
*zip new/zip NEWFILE |
| 56 |
will create an archive containing 3 copies of the same Risc OS file 'newfile' |
| 57 |
called 'newfile', 'NewFile' and 'NEWFILE'. Please be careful. |
| 58 |
|
| 59 |
The Acorn port conserves file attributes, including filetype, so if you |
| 60 |
zip on an Acorn, and unzip on another Acorn, filetypes will be maintained |
| 61 |
precisely as if you used uncompressed files. If you de-archive on another |
| 62 |
machine (PC, Mac, Unix etc..), filetypes will be ignored, but the files |
| 63 |
will be identical despite this. This feature is fully compatible with |
| 64 |
SparkFS, so zipfiles created by zip will be correctly uncompressed (including |
| 65 |
filetype, etc.) by SparkFS. |
| 66 |
|
| 67 |
An additional feature went into this port to cope better with C-code |
| 68 |
and extensions. This allows the acorn files "c.foo" to be added to the |
| 69 |
archive as "foo/c", eventually appearing in the archive as "foo.c", allowing |
| 70 |
for better handling of C or C++ code. Example: |
| 71 |
*Set Zip$Exts "dir1:dir2:dir3" |
| 72 |
*zip new/zip dir1.file |
| 73 |
*zip new/zip dir2.help |
| 74 |
*zip new/zip dir3.textfile |
| 75 |
Creates a zipfile new/zip, with entries file.dir1, help.dir2, textfile.dir3. |
| 76 |
The usual settings for Zip$Exts are "h:o:s:c", allowing C code to be added |
| 77 |
to the archive in standard form. |
| 78 |
|
| 79 |
A final note about the Acorn port regards the use of the 'n' option: this is |
| 80 |
used to specify a list of suffixes that will not be compressed (eg. .ZIP, |
| 81 |
since it is already a compressed file). Since RISC OS uses filetypes instead |
| 82 |
of suffixes, this list of suffixes is actually considered as a list of |
| 83 |
filetypes (3 hex digit format). By default, zip doesn't compress filetypes |
| 84 |
DDC (Archive, Spark or Zip), D96 (CFS files) and 68E (PackDir). |
| 85 |
|