Skip to content

Latest commit

 

History

History
1830 lines (1647 loc) · 66.8 KB

physfs.h

File metadata and controls

1830 lines (1647 loc) · 66.8 KB
 
Jun 7, 2002
Jun 7, 2002
1
2
/** \file physfs.h */
Jun 7, 2001
Jun 7, 2001
3
/**
Jun 7, 2002
Jun 7, 2002
4
5
6
7
8
* \mainpage PhysicsFS
*
* The latest version of PhysicsFS can be found at:
* http://icculus.org/physfs/
*
Jun 7, 2001
Jun 7, 2001
9
10
11
12
13
14
15
16
17
18
19
* PhysicsFS; a portable, flexible file i/o abstraction.
*
* This API gives you access to a system file system in ways superior to the
* stdio or system i/o calls. The brief benefits:
*
* - It's portable.
* - It's safe. No file access is permitted outside the specified dirs.
* - It's flexible. Archives (.ZIP files) can be used transparently as
* directory structures.
*
* This system is largely inspired by Quake 3's PK3 files and the related
Jun 7, 2001
Jun 7, 2001
20
* fs_* cvars. If you've ever tinkered with these, then this API will be
Jun 7, 2001
Jun 7, 2001
21
22
* familiar to you.
*
Jul 5, 2001
Jul 5, 2001
23
24
25
26
27
28
* With PhysicsFS, you have a single writing directory and multiple
* directories (the "search path") for reading. You can think of this as a
* filesystem within a filesystem. If (on Windows) you were to set the
* writing directory to "C:\MyGame\MyWritingDirectory", then no PHYSFS calls
* could touch anything above this directory, including the "C:\MyGame" and
* "C:\" directories. This prevents an application's internal scripting
Jan 8, 2004
Jan 8, 2004
29
* language from piddling over c:\\config.sys, for example. If you'd rather
Jul 5, 2001
Jul 5, 2001
30
31
* give PHYSFS full access to the system's REAL file system, set the writing
* dir to "C:\", but that's generally A Bad Thing for several reasons.
Jun 7, 2001
Jun 7, 2001
32
33
*
* Drive letters are hidden in PhysicsFS once you set up your initial paths.
Jul 5, 2001
Jul 5, 2001
34
* The search path creates a single, hierarchical directory structure.
Jun 7, 2001
Jun 7, 2001
35
36
37
38
39
40
41
* Not only does this lend itself well to general abstraction with archives,
* it also gives better support to operating systems like MacOS and Unix.
* Generally speaking, you shouldn't ever hardcode a drive letter; not only
* does this hurt portability to non-Microsoft OSes, but it limits your win32
* users to a single drive, too. Use the PhysicsFS abstraction functions and
* allow user-defined configuration options, too. When opening a file, you
* specify it like it was on a Unix filesystem: if you want to write to
Jul 5, 2001
Jul 5, 2001
42
* "C:\MyGame\MyConfigFiles\game.cfg", then you might set the write dir to
Jun 7, 2001
Jun 7, 2001
43
* "C:\MyGame" and then open "MyConfigFiles/game.cfg". This gives an
Jun 7, 2001
Jun 7, 2001
44
* abstraction across all platforms. Specifying a file in this way is termed
Jul 5, 2001
Jul 5, 2001
45
46
47
48
49
50
51
52
* "platform-independent notation" in this documentation. Specifying a
* a filename in a form such as "C:\mydir\myfile" or
* "MacOS hard drive:My Directory:My File" is termed "platform-dependent
* notation". The only time you use platform-dependent notation is when
* setting up your write directory and search path; after that, all file
* access into those directories are done with platform-independent notation.
*
* All files opened for writing are opened in relation to the write directory,
Jun 7, 2001
Jun 7, 2001
53
* which is the root of the writable filesystem. When opening a file for
Jul 5, 2001
Jul 5, 2001
54
* reading, PhysicsFS goes through the search path. This is NOT the
Jun 7, 2001
Jun 7, 2001
55
56
57
58
59
60
* same thing as the PATH environment variable. An application using
* PhysicsFS specifies directories to be searched which may be actual
* directories, or archive files that contain files and subdirectories of
* their own. See the end of these docs for currently supported archive
* formats.
*
Jul 5, 2001
Jul 5, 2001
61
* Once the search path is defined, you may open files for reading. If you've
Jun 7, 2001
Jun 7, 2001
62
63
* got the following search path defined (to use a win32 example again):
*
Jan 8, 2004
Jan 8, 2004
64
65
66
67
* - C:\\mygame
* - C:\\mygame\\myuserfiles
* - D:\\mygamescdromdatafiles
* - C:\\mygame\\installeddatafiles.zip
Jun 7, 2001
Jun 7, 2001
68
*
Jul 5, 2001
Jul 5, 2001
69
* Then a call to PHYSFS_openRead("textfiles/myfile.txt") (note the directory
Jun 7, 2001
Jun 7, 2001
70
71
* separator, lack of drive letter, and lack of dir separator at the start of
* the string; this is platform-independent notation) will check for
Jan 8, 2004
Jan 8, 2004
72
73
74
75
76
77
78
* C:\\mygame\\textfiles\\myfile.txt, then
* C:\\mygame\\myuserfiles\\textfiles\\myfile.txt, then
* D:\\mygamescdromdatafiles\\textfiles\\myfile.txt, then, finally, for
* textfiles\\myfile.txt inside of C:\\mygame\\installeddatafiles.zip.
* Remember that most archive types and platform filesystems store their
* filenames in a case-sensitive manner, so you should be careful to specify
* it correctly.
Jun 7, 2001
Jun 7, 2001
79
*
Jul 5, 2001
Jul 5, 2001
80
81
82
83
84
85
86
87
88
89
90
91
92
93
* Files opened through PhysicsFS may NOT contain "." or ".." or ":" as dir
* elements. Not only are these meaningless on MacOS and/or Unix, they are a
* security hole. Also, symbolic links (which can be found in some archive
* types and directly in the filesystem on Unix platforms) are NOT followed
* until you call PHYSFS_permitSymbolicLinks(). That's left to your own
* discretion, as following a symlink can allow for access outside the write
* dir and search paths. There is no mechanism for creating new symlinks in
* PhysicsFS.
*
* The write dir is not included in the search path unless you specifically
* add it. While you CAN change the write dir as many times as you like,
* you should probably set it once and stick to it. Remember that your
* program will not have permission to write in every directory on Unix and
* NT systems.
Jun 7, 2001
Jun 7, 2001
94
95
96
*
* All files are opened in binary mode; there is no endline conversion for
* textfiles. Other than that, PhysicsFS has some convenience functions for
Jun 28, 2001
Jun 28, 2001
97
* platform-independence. There is a function to tell you the current
Jul 5, 2001
Jul 5, 2001
98
* platform's dir separator ("\\" on windows, "/" on Unix, ":" on MacOS),
Jun 28, 2001
Jun 28, 2001
99
100
101
* which is needed only to set up your search/write paths. There is a
* function to tell you what CD-ROM drives contain accessible discs, and a
* function to recommend a good search path, etc.
Jun 7, 2001
Jun 7, 2001
102
*
Jul 5, 2001
Jul 5, 2001
103
104
* A recommended order for the search path is the write dir, then the base dir,
* then the cdrom dir, then any archives discovered. Quake 3 does something
Jun 28, 2001
Jun 28, 2001
105
106
* like this, but moves the archives to the start of the search path. Build
* Engine games, like Duke Nukem 3D and Blood, place the archives last, and
Jul 5, 2001
Jul 5, 2001
107
108
* use the base dir for both searching and writing. There is a helper
* function (PHYSFS_setSaneConfig()) that puts together a basic configuration
Jun 28, 2001
Jun 28, 2001
109
* for you, based on a few parameters. Also see the comments on
Jul 5, 2001
Jul 5, 2001
110
111
112
* PHYSFS_getBaseDir(), and PHYSFS_getUserDir() for info on what those
* are and how they can help you determine an optimal search path.
*
Mar 30, 2002
Mar 30, 2002
113
114
115
116
117
118
* PhysicsFS is mostly thread safe. The error messages returned by
* PHYSFS_getLastError are unique by thread, and library-state-setting
* functions are mutex'd. For efficiency, individual file accesses are
* not locked, so you can not safely read/write/seek/close/etc the same
* file from two threads at the same time. Other race conditions are bugs
* that should be reported/patched.
Jun 28, 2001
Jun 28, 2001
119
120
121
*
* While you CAN use stdio/syscall file access in a program that has PHYSFS_*
* calls, doing so is not recommended, and you can not use system
Mar 30, 2002
Mar 30, 2002
122
* filehandles with PhysicsFS and vice versa.
Jun 7, 2001
Jun 7, 2001
123
124
*
* Note that archives need not be named as such: if you have a ZIP file and
Jun 28, 2001
Jun 28, 2001
125
* rename it with a .PKG extension, the file will still be recognized as a
Jun 7, 2001
Jun 7, 2001
126
127
128
129
130
* ZIP archive by PhysicsFS; the file's contents are used to determine its
* type.
*
* Currently supported archive types:
* - .ZIP (pkZip/WinZip/Info-ZIP compatible)
Jun 7, 2002
Jun 7, 2002
131
* - .GRP (Build Engine groupfile archives)
Mar 30, 2003
Mar 30, 2003
132
* - .PAK (Quake I/II archive format)
Mar 30, 2003
Mar 30, 2003
133
134
* - .HOG (Descent I/II HOG file archives)
* - .MVL (Descent II movielib archives)
Dec 15, 2003
Dec 15, 2003
135
* - .WAD (DOOM engine archives)
Jun 7, 2002
Jun 7, 2002
136
137
138
*
* Please see the file LICENSE in the source's root directory for licensing
* and redistribution rights.
Jun 7, 2001
Jun 7, 2001
139
*
Jun 7, 2002
Jun 7, 2002
140
141
* Please see the file CREDITS in the source's root directory for a complete
* list of who's responsible for this.
Jun 7, 2001
Jun 7, 2001
142
*
Jun 7, 2002
Jun 7, 2002
143
* \author Ryan C. Gordon.
Jun 7, 2001
Jun 7, 2001
144
145
146
147
148
149
150
151
152
*/
#ifndef _INCLUDE_PHYSFS_H_
#define _INCLUDE_PHYSFS_H_
#ifdef __cplusplus
extern "C" {
#endif
Jun 7, 2002
Jun 7, 2002
153
#ifndef DOXYGEN_SHOULD_IGNORE_THIS
Aug 23, 2001
Aug 23, 2001
154
155
156
157
158
#if (defined _MSC_VER)
#define __EXPORT__ __declspec(dllexport)
#else
#define __EXPORT__
#endif
Jun 7, 2002
Jun 7, 2002
159
#endif /* DOXYGEN_SHOULD_IGNORE_THIS */
Aug 23, 2001
Aug 23, 2001
160
Jun 7, 2002
Jun 7, 2002
161
162
163
164
/**
* \typedef PHYSFS_uint8
* \brief An unsigned, 8-bit integer type.
*/
Mar 24, 2002
Mar 24, 2002
165
typedef unsigned char PHYSFS_uint8;
Jun 7, 2002
Jun 7, 2002
166
167
168
169
170
/**
* \typedef PHYSFS_sint8
* \brief A signed, 8-bit integer type.
*/
Mar 24, 2002
Mar 24, 2002
171
typedef signed char PHYSFS_sint8;
Jun 7, 2002
Jun 7, 2002
172
173
174
175
176
/**
* \typedef PHYSFS_uint16
* \brief An unsigned, 16-bit integer type.
*/
Mar 24, 2002
Mar 24, 2002
177
typedef unsigned short PHYSFS_uint16;
Jun 7, 2002
Jun 7, 2002
178
179
180
181
182
/**
* \typedef PHYSFS_sint16
* \brief A signed, 16-bit integer type.
*/
Mar 24, 2002
Mar 24, 2002
183
typedef signed short PHYSFS_sint16;
Jun 7, 2002
Jun 7, 2002
184
185
186
187
188
/**
* \typedef PHYSFS_uint32
* \brief An unsigned, 32-bit integer type.
*/
Mar 24, 2002
Mar 24, 2002
189
typedef unsigned int PHYSFS_uint32;
Jun 7, 2002
Jun 7, 2002
190
191
192
193
194
/**
* \typedef PHYSFS_sint32
* \brief A signed, 32-bit integer type.
*/
Mar 24, 2002
Mar 24, 2002
195
196
typedef signed int PHYSFS_sint32;
Jun 7, 2002
Jun 7, 2002
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
/**
* \typedef PHYSFS_uint64
* \brief An unsigned, 64-bit integer type.
* \warning on platforms without any sort of 64-bit datatype, this is
* equivalent to PHYSFS_uint32!
*/
/**
* \typedef PHYSFS_sint64
* \brief A signed, 64-bit integer type.
* \warning on platforms without any sort of 64-bit datatype, this is
* equivalent to PHYSFS_sint32!
*/
Apr 12, 2002
Apr 12, 2002
212
#if (defined PHYSFS_NO_64BIT_SUPPORT) /* oh well. */
Mar 24, 2002
Mar 24, 2002
213
214
typedef PHYSFS_uint32 PHYSFS_uint64;
typedef PHYSFS_sint32 PHYSFS_sint64;
Apr 12, 2002
Apr 12, 2002
215
216
217
#elif (defined _MSC_VER)
typedef signed __int64 PHYSFS_sint64;
typedef unsigned __int64 PHYSFS_uint64;
Mar 24, 2002
Mar 24, 2002
218
219
220
221
222
#else
typedef unsigned long long PHYSFS_uint64;
typedef signed long long PHYSFS_sint64;
#endif
Jun 7, 2002
Jun 7, 2002
223
224
#ifndef DOXYGEN_SHOULD_IGNORE_THIS
Mar 24, 2002
Mar 24, 2002
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
/* Make sure the types really have the right sizes */
#define PHYSFS_COMPILE_TIME_ASSERT(name, x) \
typedef int PHYSFS_dummy_ ## name[(x) * 2 - 1]
PHYSFS_COMPILE_TIME_ASSERT(uint8, sizeof(PHYSFS_uint8) == 1);
PHYSFS_COMPILE_TIME_ASSERT(sint8, sizeof(PHYSFS_sint8) == 1);
PHYSFS_COMPILE_TIME_ASSERT(uint16, sizeof(PHYSFS_uint16) == 2);
PHYSFS_COMPILE_TIME_ASSERT(sint16, sizeof(PHYSFS_sint16) == 2);
PHYSFS_COMPILE_TIME_ASSERT(uint32, sizeof(PHYSFS_uint32) == 4);
PHYSFS_COMPILE_TIME_ASSERT(sint32, sizeof(PHYSFS_sint32) == 4);
#ifndef PHYSFS_NO_64BIT_SUPPORT
PHYSFS_COMPILE_TIME_ASSERT(uint64, sizeof(PHYSFS_uint64) == 8);
PHYSFS_COMPILE_TIME_ASSERT(sint64, sizeof(PHYSFS_sint64) == 8);
#endif
#undef PHYSFS_COMPILE_TIME_ASSERT
Jun 7, 2002
Jun 7, 2002
243
#endif /* DOXYGEN_SHOULD_IGNORE_THIS */
Mar 24, 2002
Mar 24, 2002
244
245
Jun 7, 2002
Jun 7, 2002
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
/**
* \struct PHYSFS_file
* \brief A PhysicsFS file handle.
*
* You get a pointer to one of these when you open a file for reading,
* writing, or appending via PhysicsFS.
*
* As you can see from the lack of meaningful fields, you should treat this
* as opaque data. Don't try to manipulate the file handle, just pass the
* pointer you got, unmolested, to various PhysicsFS APIs.
*
* \sa PHYSFS_openRead
* \sa PHYSFS_openWrite
* \sa PHYSFS_openAppend
* \sa PHYSFS_close
* \sa PHYSFS_read
* \sa PHYSFS_write
* \sa PHYSFS_seek
* \sa PHYSFS_tell
* \sa PHYSFS_eof
Dec 1, 2002
Dec 1, 2002
266
267
* \sa PHYSFS_setBuffer
* \sa PHYSFS_flush
Jun 7, 2002
Jun 7, 2002
268
269
*/
typedef struct
Jun 28, 2001
Jun 28, 2001
270
{
Jun 7, 2002
Jun 7, 2002
271
void *opaque; /**< That's all you get. Don't touch. */
Jun 28, 2001
Jun 28, 2001
272
273
274
275
} PHYSFS_file;
Jun 7, 2002
Jun 7, 2002
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
/**
* \struct PHYSFS_ArchiveInfo
* \brief Information on various PhysicsFS-supported archives.
*
* This structure gives you details on what sort of archives are supported
* by this implementation of PhysicsFS. Archives tend to be things like
* ZIP files and such.
*
* \warning Not all binaries are created equal! PhysicsFS can be built with
* or without support for various archives. You can check with
* PHYSFS_supportedArchiveTypes() to see if your archive type is
* supported.
*
* \sa PHYSFS_supportedArchiveTypes
*/
typedef struct
{
const char *extension; /**< Archive file extension: "ZIP", for example. */
const char *description; /**< Human-readable archive description. */
const char *author; /**< Person who did support for this archive. */
const char *url; /**< URL related to this archive */
} PHYSFS_ArchiveInfo;
Jun 7, 2001
Jun 7, 2001
298
Dec 1, 2002
Dec 1, 2002
299
Jun 7, 2002
Jun 7, 2002
300
301
302
303
304
305
306
307
308
309
310
311
312
313
/**
* \struct PHYSFS_Version
* \brief Information the version of PhysicsFS in use.
*
* Represents the library's version as three levels: major revision
* (increments with massive changes, additions, and enhancements),
* minor revision (increments with backwards-compatible changes to the
* major revision), and patchlevel (increments with fixes to the minor
* revision).
*
* \sa PHYSFS_VERSION
* \sa PHYFS_getLinkedVersion
*/
typedef struct
Jul 5, 2001
Jul 5, 2001
314
{
Jun 7, 2002
Jun 7, 2002
315
316
317
PHYSFS_uint8 major; /**< major revision */
PHYSFS_uint8 minor; /**< minor revision */
PHYSFS_uint8 patch; /**< patchlevel */
Jul 5, 2001
Jul 5, 2001
318
319
} PHYSFS_Version;
Jun 7, 2002
Jun 7, 2002
320
#ifndef DOXYGEN_SHOULD_IGNORE_THIS
Jan 8, 2004
Jan 8, 2004
321
322
323
#define PHYSFS_VER_MAJOR 1
#define PHYSFS_VER_MINOR 0
#define PHYSFS_VER_PATCH 0
Jun 7, 2002
Jun 7, 2002
324
325
#endif /* DOXYGEN_SHOULD_IGNORE_THIS */
Dec 1, 2002
Dec 1, 2002
326
327
328
/* PhysicsFS state stuff ... */
Jun 7, 2002
Jun 7, 2002
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
/**
* \def PHYSFS_VERSION(x)
* \brief Macro to determine PhysicsFS version program was compiled against.
*
* This macro fills in a PHYSFS_Version structure with the version of the
* library you compiled against. This is determined by what header the
* compiler uses. Note that if you dynamically linked the library, you might
* have a slightly newer or older version at runtime. That version can be
* determined with PHYSFS_getLinkedVersion(), which, unlike PHYSFS_VERSION,
* is not a macro.
*
* \param x A pointer to a PHYSFS_Version struct to initialize.
*
* \sa PHYSFS_Version
* \sa PHYSFS_getLinkedVersion
*/
#define PHYSFS_VERSION(x) \
{ \
(x)->major = PHYSFS_VER_MAJOR; \
(x)->minor = PHYSFS_VER_MINOR; \
(x)->patch = PHYSFS_VER_PATCH; \
}
Jul 5, 2001
Jul 5, 2001
351
352
353
/**
Jun 7, 2002
Jun 7, 2002
354
355
356
357
358
* \fn void PHYSFS_getLinkedVersion(PHYSFS_Version *ver)
* \brief Get the version of PhysicsFS that is linked against your program.
*
* If you are using a shared library (DLL) version of PhysFS, then it is
* possible that it will be different than the version you compiled against.
Jul 5, 2001
Jul 5, 2001
359
360
361
362
*
* This is a real function; the macro PHYSFS_VERSION tells you what version
* of PhysFS you compiled against:
*
Jun 7, 2002
Jun 7, 2002
363
* \code
Jul 5, 2001
Jul 5, 2001
364
365
366
367
368
369
370
371
372
* PHYSFS_Version compiled;
* PHYSFS_Version linked;
*
* PHYSFS_VERSION(&compiled);
* PHYSFS_getLinkedVersion(&linked);
* printf("We compiled against PhysFS version %d.%d.%d ...\n",
* compiled.major, compiled.minor, compiled.patch);
* printf("But we linked against PhysFS version %d.%d.%d.\n",
* linked.major, linked.minor, linked.patch);
Jun 7, 2002
Jun 7, 2002
373
* \endcode
Jul 5, 2001
Jul 5, 2001
374
375
*
* This function may be called safely at any time, even before PHYSFS_init().
Jun 7, 2002
Jun 7, 2002
376
377
*
* \sa PHYSFS_VERSION
Jul 5, 2001
Jul 5, 2001
378
*/
Aug 23, 2001
Aug 23, 2001
379
__EXPORT__ void PHYSFS_getLinkedVersion(PHYSFS_Version *ver);
Jul 5, 2001
Jul 5, 2001
380
381
Jun 7, 2001
Jun 7, 2001
382
/**
Jun 7, 2002
Jun 7, 2002
383
384
385
386
* \fn int PHYSFS_init(const char *argv0)
* \brief Initialize the PhysicsFS library.
*
* This must be called before any other PhysicsFS function.
Jun 7, 2001
Jun 7, 2001
387
*
Jul 8, 2001
Jul 8, 2001
388
389
390
* This should be called prior to any attempts to change your process's
* current working directory.
*
Jun 7, 2002
Jun 7, 2002
391
392
393
394
395
396
* \param argv0 the argv[0] string passed to your program's mainline.
* This may be NULL on most platforms (such as ones without a
* standard main() function), but you should always try to pass
* something in here. Unix-like systems such as Linux _need_ to
* pass argv[0] from main() in here.
* \return nonzero on success, zero on error. Specifics of the error can be
Jun 7, 2001
Jun 7, 2001
397
* gleaned from PHYSFS_getLastError().
Jun 7, 2002
Jun 7, 2002
398
399
*
* \sa PHYSFS_deinit
Jun 7, 2001
Jun 7, 2001
400
*/
Aug 23, 2001
Aug 23, 2001
401
__EXPORT__ int PHYSFS_init(const char *argv0);
Jun 7, 2001
Jun 7, 2001
402
403
404
/**
Jun 7, 2002
Jun 7, 2002
405
406
407
408
409
* \fn int PHYSFS_deinit(void)
* \brief Deinitialize the PhysicsFS library.
*
* This closes any files opened via PhysicsFS, blanks the search/write paths,
* frees memory, and invalidates all of your file handles.
Jun 7, 2001
Jun 7, 2001
410
*
Jul 7, 2001
Jul 7, 2001
411
412
413
414
415
416
* Note that this call can FAIL if there's a file open for writing that
* refuses to close (for example, the underlying operating system was
* buffering writes to network filesystem, and the fileserver has crashed,
* or a hard drive has failed, etc). It is usually best to close all write
* handles yourself before calling this function, so that you can gracefully
* handle a specific failure.
Jun 7, 2001
Jun 7, 2001
417
*
Jul 7, 2001
Jul 7, 2001
418
419
420
* Once successfully deinitialized, PHYSFS_init() can be called again to
* restart the subsystem. All defaults API states are restored at this
* point.
Jul 5, 2001
Jul 5, 2001
421
*
Jun 7, 2002
Jun 7, 2002
422
* \return nonzero on success, zero on error. Specifics of the error can be
Jun 7, 2001
Jun 7, 2001
423
424
* gleaned from PHYSFS_getLastError(). If failure, state of PhysFS is
* undefined, and probably badly screwed up.
Jun 7, 2002
Jun 7, 2002
425
426
*
* \sa PHYSFS_init
Jun 7, 2001
Jun 7, 2001
427
*/
Aug 23, 2001
Aug 23, 2001
428
__EXPORT__ int PHYSFS_deinit(void);
Jun 7, 2001
Jun 7, 2001
429
Jun 7, 2001
Jun 7, 2001
430
Jun 28, 2001
Jun 28, 2001
431
/**
Jun 7, 2002
Jun 7, 2002
432
433
434
* \fn const PHYSFS_ArchiveInfo **PHYSFS_supportedArchiveTypes(void)
* \brief Get a list of supported archive types.
*
Jun 28, 2001
Jun 28, 2001
435
436
437
438
439
440
* Get a list of archive types supported by this implementation of PhysicFS.
* These are the file formats usable for search path entries. This is for
* informational purposes only. Note that the extension listed is merely
* convention: if we list "ZIP", you can open a PkZip-compatible archive
* with an extension of "XYZ", if you like.
*
Jul 5, 2001
Jul 5, 2001
441
442
* The returned value is an array of pointers to PHYSFS_ArchiveInfo structures,
* with a NULL entry to signify the end of the list:
Jun 28, 2001
Jun 28, 2001
443
*
Jun 7, 2002
Jun 7, 2002
444
* \code
Jun 28, 2001
Jun 28, 2001
445
446
447
448
449
450
451
* PHYSFS_ArchiveInfo **i;
*
* for (i = PHYSFS_supportedArchiveTypes(); *i != NULL; i++)
* {
* printf("Supported archive: [%s], which is [%s].\n",
* i->extension, i->description);
* }
Jun 7, 2002
Jun 7, 2002
452
* \endcode
Jun 28, 2001
Jun 28, 2001
453
454
455
456
*
* The return values are pointers to static internal memory, and should
* be considered READ ONLY, and never freed.
*
Jun 7, 2002
Jun 7, 2002
457
* \return READ ONLY Null-terminated array of READ ONLY structures.
Jun 28, 2001
Jun 28, 2001
458
*/
Aug 23, 2001
Aug 23, 2001
459
__EXPORT__ const PHYSFS_ArchiveInfo **PHYSFS_supportedArchiveTypes(void);
Jun 28, 2001
Jun 28, 2001
460
461
462
/**
Jun 7, 2002
Jun 7, 2002
463
464
465
* \fn void PHYSFS_freeList(void *listVar)
* \brief Deallocate resources of lists returned by PhysicsFS.
*
Jun 28, 2001
Jun 28, 2001
466
467
468
* Certain PhysicsFS functions return lists of information that are
* dynamically allocated. Use this function to free those resources.
*
Jun 7, 2002
Jun 7, 2002
469
470
471
472
473
* \param listVar List of information specified as freeable by this function.
*
* \sa PHYSFS_getCdRomDirs
* \sa PHYSFS_enumerateFiles
* \sa PHYSFS_getSearchPath
Jun 28, 2001
Jun 28, 2001
474
*/
Mar 21, 2002
Mar 21, 2002
475
__EXPORT__ void PHYSFS_freeList(void *listVar);
Jun 28, 2001
Jun 28, 2001
476
477
Jun 7, 2001
Jun 7, 2001
478
/**
Jun 7, 2002
Jun 7, 2002
479
480
481
* \fn const char *PHYSFS_getLastError(void)
* \brief Get human-readable error information.
*
Jun 7, 2001
Jun 7, 2001
482
483
* Get the last PhysicsFS error message as a null-terminated string.
* This will be NULL if there's been no error since the last call to this
Jul 5, 2001
Jul 5, 2001
484
485
486
487
488
* function. The pointer returned by this call points to an internal buffer.
* Each thread has a unique error state associated with it, but each time
* a new error message is set, it will overwrite the previous one associated
* with that thread. It is safe to call this function at anytime, even
* before PHYSFS_init().
Jun 7, 2001
Jun 7, 2001
489
*
Jun 7, 2002
Jun 7, 2002
490
* \return READ ONLY string of last error message.
Jun 7, 2001
Jun 7, 2001
491
*/
Aug 23, 2001
Aug 23, 2001
492
__EXPORT__ const char *PHYSFS_getLastError(void);
Jun 7, 2001
Jun 7, 2001
493
494
495
/**
Jun 7, 2002
Jun 7, 2002
496
497
* \fn const char *PHYSFS_getDirSeparator(void)
* \brief Get platform-dependent dir separator string.
Jun 7, 2001
Jun 7, 2001
498
*
Jun 7, 2002
Jun 7, 2002
499
500
501
502
503
504
505
506
* This returns "\\\\" on win32, "/" on Unix, and ":" on MacOS. It may be more
* than one character, depending on the platform, and your code should take
* that into account. Note that this is only useful for setting up the
* search/write paths, since access into those dirs always use '/'
* (platform-independent notation) to separate directories. This is also
* handy for getting platform-independent access when using stdio calls.
*
* \return READ ONLY null-terminated string of platform's dir separator.
Jun 7, 2001
Jun 7, 2001
507
*/
Aug 23, 2001
Aug 23, 2001
508
__EXPORT__ const char *PHYSFS_getDirSeparator(void);
Jun 7, 2001
Jun 7, 2001
509
510
Jul 7, 2001
Jul 7, 2001
511
/**
Jun 7, 2002
Jun 7, 2002
512
513
514
515
516
517
* \fn void PHYSFS_permitSymbolicLinks(int allow)
* \brief Enable or disable following of symbolic links.
*
* Some physical filesystems and archives contain files that are just pointers
* to other files. On the physical filesystem, opening such a link will
* (transparently) open the file that is pointed to.
Jul 7, 2001
Jul 7, 2001
518
519
520
521
522
523
524
525
526
527
528
529
*
* By default, PhysicsFS will check if a file is really a symlink during open
* calls and fail if it is. Otherwise, the link could take you outside the
* write and search paths, and compromise security.
*
* If you want to take that risk, call this function with a non-zero parameter.
* Note that this is more for sandboxing a program's scripting language, in
* case untrusted scripts try to compromise the system. Generally speaking,
* a user could very well have a legitimate reason to set up a symlink, so
* unless you feel there's a specific danger in allowing them, you should
* permit them.
*
Jul 16, 2001
Jul 16, 2001
530
531
532
533
* Symlinks are only explicitly checked when dealing with filenames
* in platform-independent notation. That is, when setting up your
* search and write paths, etc, symlinks are never checked for.
*
Jun 7, 2002
Jun 7, 2002
534
535
* Symbolic link permission can be enabled or disabled at any time after
* you've called PHYSFS_init(), and is disabled by default.
Jul 7, 2001
Jul 7, 2001
536
*
Jun 7, 2002
Jun 7, 2002
537
* \param allow nonzero to permit symlinks, zero to deny linking.
Jul 7, 2001
Jul 7, 2001
538
*/
Aug 23, 2001
Aug 23, 2001
539
__EXPORT__ void PHYSFS_permitSymbolicLinks(int allow);
Jul 7, 2001
Jul 7, 2001
540
541
Jun 7, 2001
Jun 7, 2001
542
/**
Jun 7, 2002
Jun 7, 2002
543
544
* \fn char **PHYSFS_getCdRomDirs(void)
* \brief Get an array of paths to available CD-ROM drives.
Jun 7, 2001
Jun 7, 2001
545
*
Jul 5, 2001
Jul 5, 2001
546
547
* The dirs returned are platform-dependent ("D:\" on Win32, "/cdrom" or
* whatnot on Unix). Dirs are only returned if there is a disc ready and
Jun 7, 2001
Jun 7, 2001
548
549
550
551
552
553
554
555
556
* accessible in the drive. So if you've got two drives (D: and E:), and only
* E: has a disc in it, then that's all you get. If the user inserts a disc
* in D: and you call this function again, you get both drives. If, on a
* Unix box, the user unmounts a disc and remounts it elsewhere, the next
* call to this function will reflect that change. Fun.
*
* The returned value is an array of strings, with a NULL entry to signify the
* end of the list:
*
Jun 7, 2002
Jun 7, 2002
557
* \code
Jul 6, 2001
Jul 6, 2001
558
* char **cds = PHYSFS_getCdRomDirs();
Jun 7, 2001
Jun 7, 2001
559
560
* char **i;
*
Jul 6, 2001
Jul 6, 2001
561
* for (i = cds; *i != NULL; i++)
Jul 5, 2001
Jul 5, 2001
562
* printf("cdrom dir [%s] is available.\n", *i);
Jun 7, 2001
Jun 7, 2001
563
*
Jul 6, 2001
Jul 6, 2001
564
* PHYSFS_freeList(cds);
Jun 7, 2002
Jun 7, 2002
565
* \endcode
Jul 6, 2001
Jul 6, 2001
566
*
Jun 7, 2001
Jun 7, 2001
567
568
* This call may block while drives spin up. Be forewarned.
*
Jun 28, 2001
Jun 28, 2001
569
570
571
* When you are done with the returned information, you may dispose of the
* resources by calling PHYSFS_freeList() with the returned pointer.
*
Jun 7, 2002
Jun 7, 2002
572
* \return Null-terminated array of null-terminated strings.
Jun 7, 2001
Jun 7, 2001
573
*/
Aug 23, 2001
Aug 23, 2001
574
__EXPORT__ char **PHYSFS_getCdRomDirs(void);
Jun 7, 2001
Jun 7, 2001
575
576
577
/**
Jun 7, 2002
Jun 7, 2002
578
579
580
* \fn const char *PHYSFS_getBaseDir(void)
* \brief Get the path where the application resides.
*
Jun 7, 2001
Jun 7, 2001
581
582
* Helper function.
*
Jul 5, 2001
Jul 5, 2001
583
* Get the "base dir". This is the directory where the application was run
Jun 28, 2001
Jun 28, 2001
584
585
* from, which is probably the installation directory, and may or may not
* be the process's current working directory.
Jun 7, 2001
Jun 7, 2001
586
*
Jul 5, 2001
Jul 5, 2001
587
* You should probably use the base dir in your search path.
Jun 7, 2001
Jun 7, 2001
588
*
Jun 7, 2002
Jun 7, 2002
589
590
591
* \return READ ONLY string of base dir in platform-dependent notation.
*
* \sa PHYSFS_getUserDir
Jun 7, 2001
Jun 7, 2001
592
*/
Aug 23, 2001
Aug 23, 2001
593
__EXPORT__ const char *PHYSFS_getBaseDir(void);
Jun 7, 2001
Jun 7, 2001
594
595
596
/**
Jun 7, 2002
Jun 7, 2002
597
598
599
* \fn const char *PHYSFS_getUserDir(void)
* \brief Get the path where user's home directory resides.
*
Jun 7, 2001
Jun 7, 2001
600
601
* Helper function.
*
Jul 5, 2001
Jul 5, 2001
602
* Get the "user dir". This is meant to be a suggestion of where a specific
Jun 7, 2001
Jun 7, 2001
603
* user of the system can store files. On Unix, this is her home directory.
Jun 28, 2001
Jun 28, 2001
604
* On systems with no concept of multiple home directories (MacOS, win95),
Jul 5, 2001
Jul 5, 2001
605
* this will default to something like "C:\mybasedir\users\username"
Jun 28, 2001
Jun 28, 2001
606
607
* where "username" will either be the login name, or "default" if the
* platform doesn't support multiple users, either.
Jun 7, 2001
Jun 7, 2001
608
*
Jul 5, 2001
Jul 5, 2001
609
* You should probably use the user dir as the basis for your write dir, and
Jun 7, 2001
Jun 7, 2001
610
611
* also put it near the beginning of your search path.
*
Jun 7, 2002
Jun 7, 2002
612
613
614
* \return READ ONLY string of user dir in platform-dependent notation.
*
* \sa PHYSFS_getBaseDir
Jun 7, 2001
Jun 7, 2001
615
*/
Aug 23, 2001
Aug 23, 2001
616
__EXPORT__ const char *PHYSFS_getUserDir(void);
Jun 7, 2001
Jun 7, 2001
617
618
619
/**
Jun 7, 2002
Jun 7, 2002
620
621
622
* \fn const char *PHYSFS_getWriteDir(void)
* \brief Get path where PhysicsFS will allow file writing.
*
Jul 5, 2001
Jul 5, 2001
623
* Get the current write dir. The default write dir is NULL.
Jun 7, 2001
Jun 7, 2001
624
*
Jun 7, 2002
Jun 7, 2002
625
* \return READ ONLY string of write dir in platform-dependent notation,
Jun 7, 2001
Jun 7, 2001
626
* OR NULL IF NO WRITE PATH IS CURRENTLY SET.
Jun 7, 2002
Jun 7, 2002
627
628
*
* \sa PHYSFS_setWriteDir
Jun 7, 2001
Jun 7, 2001
629
*/
Aug 23, 2001
Aug 23, 2001
630
__EXPORT__ const char *PHYSFS_getWriteDir(void);
Jun 7, 2001
Jun 7, 2001
631
632
633
/**
Jun 7, 2002
Jun 7, 2002
634
635
636
* \fn int PHYSFS_setWriteDir(const char *newDir)
* \brief Tell PhysicsFS where it may write files.
*
Jul 5, 2001
Jul 5, 2001
637
* Set a new write dir. This will override the previous setting. If the
Jun 7, 2001
Jun 7, 2001
638
639
640
* directory or a parent directory doesn't exist in the physical filesystem,
* PhysicsFS will attempt to create them as needed.
*
Jul 5, 2001
Jul 5, 2001
641
642
* This call will fail (and fail to change the write dir) if the current
* write dir still has files open in it.
Jun 7, 2001
Jun 7, 2001
643
*
Jun 7, 2002
Jun 7, 2002
644
* \param newDir The new directory to be the root of the write dir,
Jun 28, 2001
Jun 28, 2001
645
* specified in platform-dependent notation. Setting to NULL
Jul 5, 2001
Jul 5, 2001
646
* disables the write dir, so no files can be opened for
Jun 7, 2001
Jun 7, 2001
647
* writing via PhysicsFS.
Jun 7, 2002
Jun 7, 2002
648
* \return non-zero on success, zero on failure. All attempts to open a file
Jun 7, 2001
Jun 7, 2001
649
650
651
* for writing via PhysicsFS will fail until this call succeeds.
* Specifics of the error can be gleaned from PHYSFS_getLastError().
*
Jun 7, 2002
Jun 7, 2002
652
* \sa PHYSFS_getWriteDir
Jun 7, 2001
Jun 7, 2001
653
*/
Aug 23, 2001
Aug 23, 2001
654
__EXPORT__ int PHYSFS_setWriteDir(const char *newDir);
Jun 7, 2001
Jun 7, 2001
655
656
657
/**
Jun 7, 2002
Jun 7, 2002
658
659
660
661
662
* \fn int PHYSFS_addToSearchPath(const char *newDir, int appendToPath)
* \brief Add an archive or directory to the search path.
*
* If this is a duplicate, the entry is not added again, even though the
* function succeeds.
Jun 7, 2001
Jun 7, 2001
663
*
Jun 7, 2002
Jun 7, 2002
664
* \param newDir directory or archive to add to the path, in
Jun 7, 2001
Jun 7, 2001
665
* platform-dependent notation.
Jun 7, 2002
Jun 7, 2002
666
667
* \param appendToPath nonzero to append to search path, zero to prepend.
* \return nonzero if added to path, zero on failure (bogus archive, dir
Jun 7, 2001
Jun 7, 2001
668
669
* missing, etc). Specifics of the error can be
* gleaned from PHYSFS_getLastError().
Jun 7, 2002
Jun 7, 2002
670
671
672
*
* \sa PHYSFS_removeFromSearchPath
* \sa PHYSFS_getSearchPath
Jun 7, 2001
Jun 7, 2001
673
*/
Aug 23, 2001
Aug 23, 2001
674
__EXPORT__ int PHYSFS_addToSearchPath(const char *newDir, int appendToPath);
Jun 7, 2001
Jun 7, 2001
675
676
677
/**
Jun 7, 2002
Jun 7, 2002
678
679
* \fn int PHYSFS_removeFromSearchPath(const char *oldDir)
* \brief Remove a directory or archive from the search path.
Jun 7, 2001
Jun 7, 2001
680
681
682
683
684
685
686
*
* This must be a (case-sensitive) match to a dir or archive already in the
* search path, specified in platform-dependent notation.
*
* This call will fail (and fail to remove from the path) if the element still
* has files open in it.
*
Jun 7, 2002
Jun 7, 2002
687
688
* \param oldDir dir/archive to remove.
* \return nonzero on success, zero on failure.
Jun 7, 2001
Jun 7, 2001
689
* Specifics of the error can be gleaned from PHYSFS_getLastError().
Jun 7, 2002
Jun 7, 2002
690
691
692
*
* \sa PHYSFS_addToSearchPath
* \sa PHYSFS_getSearchPath
Jun 7, 2001
Jun 7, 2001
693
*/
Aug 23, 2001
Aug 23, 2001
694
__EXPORT__ int PHYSFS_removeFromSearchPath(const char *oldDir);
Jun 7, 2001
Jun 7, 2001
695
696
697
/**
Jun 7, 2002
Jun 7, 2002
698
699
700
701
* \fn char **PHYSFS_getSearchPath(void)
* \brief Get the current search path.
*
* The default search path is an empty list.
Jun 7, 2001
Jun 7, 2001
702
703
704
705
*
* The returned value is an array of strings, with a NULL entry to signify the
* end of the list:
*
Jun 7, 2002
Jun 7, 2002
706
* \code
Jun 7, 2001
Jun 7, 2001
707
708
709
710
* char **i;
*
* for (i = PHYSFS_getSearchPath(); *i != NULL; i++)
* printf("[%s] is in the search path.\n", *i);
Jun 7, 2002
Jun 7, 2002
711
* \endcode
Jun 7, 2001
Jun 7, 2001
712
*
Jun 28, 2001
Jun 28, 2001
713
714
* When you are done with the returned information, you may dispose of the
* resources by calling PHYSFS_freeList() with the returned pointer.
Jun 7, 2001
Jun 7, 2001
715
*
Jun 7, 2002
Jun 7, 2002
716
* \return Null-terminated array of null-terminated strings. NULL if there
Jul 5, 2001
Jul 5, 2001
717
* was a problem (read: OUT OF MEMORY).
Jun 7, 2002
Jun 7, 2002
718
719
720
*
* \sa PHYSFS_addToSearchPath
* \sa PHYSFS_removeFromSearchPath
Jun 7, 2001
Jun 7, 2001
721
*/
Aug 23, 2001
Aug 23, 2001
722
__EXPORT__ char **PHYSFS_getSearchPath(void);
Jun 7, 2001
Jun 7, 2001
723
724
725
/**
Jun 7, 2002
Jun 7, 2002
726
727
728
* \fn int PHYSFS_setSaneConfig(const char *organization, const char *appName, const char *archiveExt, int includeCdRoms, int archivesFirst)
* \brief Set up sane, default paths.
*
Jun 7, 2001
Jun 7, 2001
729
730
* Helper function.
*
Jun 7, 2002
Jun 7, 2002
731
732
* The write dir will be set to "userdir/.organization/appName", which is
* created if it doesn't exist.
Jun 7, 2001
Jun 7, 2001
733
734
735
736
737
738
739
*
* The above is sufficient to make sure your program's configuration directory
* is separated from other clutter, and platform-independent. The period
* before "mygame" even hides the directory on Unix systems.
*
* The search path will be:
*
Jul 5, 2001
Jul 5, 2001
740
741
742
* - The Write Dir (created if it doesn't exist)
* - The Base Dir (PHYSFS_getBaseDir())
* - All found CD-ROM dirs (optionally)
Jun 7, 2001
Jun 7, 2001
743
744
745
746
747
748
749
750
751
*
* These directories are then searched for files ending with the extension
* (archiveExt), which, if they are valid and supported archives, will also
* be added to the search path. If you specified "PKG" for (archiveExt), and
* there's a file named data.PKG in the base dir, it'll be checked. Archives
* can either be appended or prepended to the search path in alphabetical
* order, regardless of which directories they were found in.
*
* All of this can be accomplished from the application, but this just does it
Jun 7, 2001
Jun 7, 2001
752
* all for you. Feel free to add more to the search path manually, too.
Jun 7, 2001
Jun 7, 2001
753
*
Jun 7, 2002
Jun 7, 2002
754
* \param organization Name of your company/group/etc to be used as a
Sep 26, 2001
Sep 26, 2001
755
756
* dirname, so keep it small, and no-frills.
*
Jun 7, 2002
Jun 7, 2002
757
* \param appName Program-specific name of your program, to separate it
Jun 7, 2001
Jun 7, 2001
758
759
* from other programs using PhysicsFS.
*
Jul 26, 2002
Jul 26, 2002
760
* \param archiveExt File extension used by your program to specify an
Jun 7, 2001
Jun 7, 2001
761
762
* archive. For example, Quake 3 uses "pk3", even though
* they are just zipfiles. Specify NULL to not dig out
Jul 6, 2001
Jul 6, 2001
763
764
765
* archives automatically. Do not specify the '.' char;
* If you want to look for ZIP files, specify "ZIP" and
* not ".ZIP" ... the archive search is case-insensitive.
Jun 7, 2001
Jun 7, 2001
766
*
Jun 7, 2002
Jun 7, 2002
767
* \param includeCdRoms Non-zero to include CD-ROMs in the search path, and
Jun 7, 2001
Jun 7, 2001
768
769
770
771
772
773
774
* (if (archiveExt) != NULL) search them for archives.
* This may cause a significant amount of blocking
* while discs are accessed, and if there are no discs
* in the drive (or even not mounted on Unix systems),
* then they may not be made available anyhow. You may
* want to specify zero and handle the disc setup
* yourself.
Jun 7, 2001
Jun 7, 2001
775
*
Jun 7, 2002
Jun 7, 2002
776
* \param archivesFirst Non-zero to prepend the archives to the search path.
Jun 7, 2001
Jun 7, 2001
777
* Zero to append them. Ignored if !(archiveExt).
Sep 26, 2001
Sep 26, 2001
778
*
Jun 7, 2002
Jun 7, 2002
779
* \return nonzero on success, zero on error. Specifics of the error can be
Jul 6, 2001
Jul 6, 2001
780
* gleaned from PHYSFS_getLastError().
Jun 7, 2001
Jun 7, 2001
781
*/
Sep 26, 2001
Sep 26, 2001
782
783
__EXPORT__ int PHYSFS_setSaneConfig(const char *organization,
const char *appName,
Aug 23, 2001
Aug 23, 2001
784
785
786
const char *archiveExt,
int includeCdRoms,
int archivesFirst);
Jun 7, 2001
Jun 7, 2001
787
788
Dec 1, 2002
Dec 1, 2002
789
790
/* Directory management stuff ... */
Jun 7, 2001
Jun 7, 2001
791
/**
Jun 7, 2002
Jun 7, 2002
792
793
794
795
796
797
* \fn int PHYSFS_mkdir(const char *dirName)
* \brief Create a directory.
*
* This is specified in platform-independent notation in relation to the
* write dir. All missing parent directories are also created if they
* don't exist.
Jun 7, 2001
Jun 7, 2001
798
*
Jul 5, 2001
Jul 5, 2001
799
* So if you've got the write dir set to "C:\mygame\writedir" and call
Jun 7, 2001
Jun 7, 2001
800
* PHYSFS_mkdir("downloads/maps") then the directories
Jul 5, 2001
Jul 5, 2001
801
* "C:\mygame\writedir\downloads" and "C:\mygame\writedir\downloads\maps"
Jun 28, 2001
Jun 28, 2001
802
803
804
* will be created if possible. If the creation of "maps" fails after we
* have successfully created "downloads", then the function leaves the
* created directory behind and reports failure.
Jun 7, 2001
Jun 7, 2001
805
*
Jun 7, 2002
Jun 7, 2002
806
807
* \param dirName New dir to create.
* \return nonzero on success, zero on error. Specifics of the error can be
Jun 7, 2001
Jun 7, 2001
808
* gleaned from PHYSFS_getLastError().
Jun 7, 2002
Jun 7, 2002
809
810
*
* \sa PHYSFS_delete
Jun 7, 2001
Jun 7, 2001
811
*/
Aug 23, 2001
Aug 23, 2001
812
__EXPORT__ int PHYSFS_mkdir(const char *dirName);
Jun 7, 2001
Jun 7, 2001
813
814
815
/**
Jun 7, 2002
Jun 7, 2002
816
817
818
819
820
* \fn int PHYSFS_delete(const char *filename)
* \brief Delete a file or directory.
*
* (filename) is specified in platform-independent notation in relation to the
* write dir.
Jun 7, 2001
Jun 7, 2001
821
*
Jun 28, 2001
Jun 28, 2001
822
* A directory must be empty before this call can delete it.
Jun 7, 2001
Jun 7, 2001
823
*
Mar 25, 2002
Mar 25, 2002
824
825
826
* Deleting a symlink will remove the link, not what it points to, regardless
* of whether you "permitSymLinks" or not.
*
Jul 5, 2001
Jul 5, 2001
827
* So if you've got the write dir set to "C:\mygame\writedir" and call
Jun 7, 2001
Jun 7, 2001
828
* PHYSFS_delete("downloads/maps/level1.map") then the file
Jul 5, 2001
Jul 5, 2001
829
* "C:\mygame\writedir\downloads\maps\level1.map" is removed from the
Jun 7, 2001
Jun 7, 2001
830
831
832
* physical filesystem, if it exists and the operating system permits the
* deletion.
*
Jun 7, 2001
Jun 7, 2001
833
834
835
836
* Note that on Unix systems, deleting a file may be successful, but the
* actual file won't be removed until all processes that have an open
* filehandle to it (including your program) close their handles.
*
Mar 25, 2002
Mar 25, 2002
837
838
839
840
* Chances are, the bits that make up the file still exist, they are just
* made available to be written over at a later point. Don't consider this
* a security method or anything. :)
*
Jun 7, 2002
Jun 7, 2002
841
842
* \param filename Filename to delete.
* \return nonzero on success, zero on error. Specifics of the error can be
Jun 7, 2001
Jun 7, 2001
843
844
* gleaned from PHYSFS_getLastError().
*/
Aug 23, 2001
Aug 23, 2001
845
__EXPORT__ int PHYSFS_delete(const char *filename);
Jun 7, 2001
Jun 7, 2001
846
847
848
/**
Jun 7, 2002
Jun 7, 2002
849
850
851
852
853
854
855
856
* \fn const char *PHYSFS_getRealDir(const char *filename)
* \brief Figure out where in the search path a file resides.
*
* The file is specified in platform-independent notation. The returned
* filename will be the element of the search path where the file was found,
* which may be a directory, or an archive. Even if there are multiple
* matches in different parts of the search path, only the first one found
* is used, just like when opening a file.
Jun 7, 2001
Jun 7, 2001
857
*
Jan 8, 2004
Jan 8, 2004
858
859
* So, if you look for "maps/level1.map", and C:\\mygame is in your search
* path and C:\\mygame\\maps\\level1.map exists, then "C:\mygame" is returned.
Jun 7, 2001
Jun 7, 2001
860
*
Jul 7, 2001
Jul 7, 2001
861
862
863
* If a any part of a match is a symbolic link, and you've not explicitly
* permitted symlinks, then it will be ignored, and the search for a match
* will continue.
Jun 7, 2001
Jun 7, 2001
864
*
Jun 7, 2002
Jun 7, 2002
865
866
* \param filename file to look for.
* \return READ ONLY string of element of search path containing the
Jun 28, 2001
Jun 28, 2001
867
868
* the file in question. NULL if not found.
*/
Aug 23, 2001
Aug 23, 2001
869
__EXPORT__ const char *PHYSFS_getRealDir(const char *filename);
Jun 28, 2001
Jun 28, 2001
870
871
872
/**
Jun 7, 2002
Jun 7, 2002
873
874
875
876
877
878
879
* \fn char **PHYSFS_enumerateFiles(const char *dir)
* \brief Get a file listing of a search path's directory.
*
* Matching directories are interpolated. That is, if "C:\mydir" is in the
* search path and contains a directory "savegames" that contains "x.sav",
* "y.sav", and "z.sav", and there is also a "C:\userdir" in the search path
* that has a "savegames" subdirectory with "w.sav", then the following code:
Jun 28, 2001
Jun 28, 2001
880
*
Jun 7, 2002
Jun 7, 2002
881
* \code
Jun 28, 2001
Jun 28, 2001
882
883
884
885
* char **rc = PHYSFS_enumerateFiles("savegames");
* char **i;
*
* for (i = rc; *i != NULL; i++)
Jun 7, 2002
Jun 7, 2002
886
* printf(" * We've got [%s].\n", *i);
Jun 28, 2001
Jun 28, 2001
887
888
*
* PHYSFS_freeList(rc);
Jun 7, 2002
Jun 7, 2002
889
* \endcode
Jun 28, 2001
Jun 28, 2001
890
891
892
*
* ...will print:
*
Jun 7, 2002
Jun 7, 2002
893
* \verbatim
Jun 28, 2001
Jun 28, 2001
894
895
896
* We've got [x.sav].
* We've got [y.sav].
* We've got [z.sav].
Jun 7, 2002
Jun 7, 2002
897
* We've got [w.sav].\endverbatim
Jun 28, 2001
Jun 28, 2001
898
*
Jul 5, 2001
Jul 5, 2001
899
900
901
* Feel free to sort the list however you like. We only promise there will
* be no duplicates, but not what order the final list will come back in.
*
Jun 28, 2001
Jun 28, 2001
902
903
904
* Don't forget to call PHYSFS_freeList() with the return value from this
* function when you are done with it.
*
Jun 7, 2002
Jun 7, 2002
905
906
* \param dir directory in platform-independent notation to enumerate.
* \return Null-terminated array of null-terminated strings.
Jun 7, 2001
Jun 7, 2001
907
*/
Aug 23, 2001
Aug 23, 2001
908
__EXPORT__ char **PHYSFS_enumerateFiles(const char *dir);
Jun 7, 2001
Jun 7, 2001
909
910
Jul 7, 2001
Jul 7, 2001
911
/**
Jun 7, 2002
Jun 7, 2002
912
913
914
915
* \fn int PHYSFS_exists(const char *fname)
* \brief Determine if a file exists in the search path.
*
* Reports true if there is an entry anywhere in the search path by the
Jul 7, 2001
Jul 7, 2001
916
917
918
919
920
921
* name of (fname).
*
* Note that entries that are symlinks are ignored if
* PHYSFS_permitSymbolicLinks(1) hasn't been called, so you
* might end up further down in the search path than expected.
*
Jun 7, 2002
Jun 7, 2002
922
923
924
925
926
* \param fname filename in platform-independent notation.
* \return non-zero if filename exists. zero otherwise.
*
* \sa PHYSFS_isDirectory
* \sa PHYSFS_isSymbolicLink
Jul 7, 2001
Jul 7, 2001
927
*/
Aug 23, 2001
Aug 23, 2001
928
__EXPORT__ int PHYSFS_exists(const char *fname);
Jul 7, 2001
Jul 7, 2001
929
930
931
/**
Jun 7, 2002
Jun 7, 2002
932
933
934
* \fn int PHYSFS_isDirectory(const char *fname)
* \brief Determine if a file in the search path is really a directory.
*
Jul 7, 2001
Jul 7, 2001
935
936
937
938
939
940
941
* Determine if the first occurence of (fname) in the search path is
* really a directory entry.
*
* Note that entries that are symlinks are ignored if
* PHYSFS_permitSymbolicLinks(1) hasn't been called, so you
* might end up further down in the search path than expected.
*
Jun 7, 2002
Jun 7, 2002
942
943
944
945
946
* \param fname filename in platform-independent notation.
* \return non-zero if filename exists and is a directory. zero otherwise.
*
* \sa PHYSFS_exists
* \sa PHYSFS_isSymbolicLink
Jul 7, 2001
Jul 7, 2001
947
*/
Aug 23, 2001
Aug 23, 2001
948
__EXPORT__ int PHYSFS_isDirectory(const char *fname);
Jul 7, 2001
Jul 7, 2001
949
950
951
/**
Jun 7, 2002
Jun 7, 2002
952
953
954
* \fn int PHYSFS_isSymbolicLink(const char *fname)
* \brief Determine if a file in the search path is really a symbolic link.
*
Jul 7, 2001
Jul 7, 2001
955
956
957
958
959
960
961
* Determine if the first occurence of (fname) in the search path is
* really a symbolic link.
*
* Note that entries that are symlinks are ignored if
* PHYSFS_permitSymbolicLinks(1) hasn't been called, and as such,
* this function will always return 0 in that case.
*
Jun 7, 2002
Jun 7, 2002
962
963
964
965
966
* \param fname filename in platform-independent notation.
* \return non-zero if filename exists and is a symlink. zero otherwise.
*
* \sa PHYSFS_exists
* \sa PHYSFS_isDirectory
Jul 7, 2001
Jul 7, 2001
967
*/
Aug 23, 2001
Aug 23, 2001
968
__EXPORT__ int PHYSFS_isSymbolicLink(const char *fname);
Jul 7, 2001
Jul 7, 2001
969
970
Dec 1, 2002
Dec 1, 2002
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
/**
* \fn PHYSFS_sint64 PHYSFS_getLastModTime(const char *filename)
* \brief Get the last modification time of a file.
*
* The modtime is returned as a number of seconds since the epoch
* (Jan 1, 1970). The exact derivation and accuracy of this time depends on
* the particular archiver. If there is no reasonable way to obtain this
* information for a particular archiver, or there was some sort of error,
* this function returns (-1).
*
* \param filename filename to check, in platform-independent notation.
* \return last modified time of the file. -1 if it can't be determined.
*/
__EXPORT__ PHYSFS_sint64 PHYSFS_getLastModTime(const char *filename);
/* i/o stuff... */
Jun 7, 2001
Jun 7, 2001
989
/**
Jun 7, 2002
Jun 7, 2002
990
991
992
* \fn PHYSFS_file *PHYSFS_openWrite(const char *filename)
* \brief Open a file for writing.
*
Jun 7, 2001
Jun 7, 2001
993
* Open a file for writing, in platform-independent notation and in relation
Jul 5, 2001
Jul 5, 2001
994
* to the write dir as the root of the writable filesystem. The specified
Jun 7, 2001
Jun 7, 2001
995
996
997
* file is created if it doesn't exist. If it does exist, it is truncated to
* zero bytes, and the writing offset is set to the start.
*
Jul 7, 2001
Jul 7, 2001
998
999
1000
* Note that entries that are symlinks are ignored if
* PHYSFS_permitSymbolicLinks(1) hasn't been called, and opening a
* symlink with this function will fail in such a case.