Skip to content

Latest commit

 

History

History
1825 lines (1642 loc) · 66.6 KB

physfs.h

File metadata and controls

1825 lines (1642 loc) · 66.6 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
29
30
31
* 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
* language from piddling over c:\config.sys, for example. If you'd rather
* 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
64
65
66
67
68
* got the following search path defined (to use a win32 example again):
*
* C:\mygame
* C:\mygame\myuserfiles
* D:\mygamescdromdatafiles
* C:\mygame\installeddatafiles.zip
*
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
72
* separator, lack of drive letter, and lack of dir separator at the start of
* the string; this is platform-independent notation) will check for
* C:\mygame\textfiles\myfile.txt, then
Jun 7, 2001
Jun 7, 2001
73
74
75
76
* 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
Jun 7, 2001
Jun 7, 2001
77
* a case-sensitive manner, so you should be careful to specify it correctly.
Jun 7, 2001
Jun 7, 2001
78
*
Jul 5, 2001
Jul 5, 2001
79
80
81
82
83
84
85
86
87
88
89
90
91
92
* 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
93
94
95
*
* 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
96
* platform-independence. There is a function to tell you the current
Jul 5, 2001
Jul 5, 2001
97
* platform's dir separator ("\\" on windows, "/" on Unix, ":" on MacOS),
Jun 28, 2001
Jun 28, 2001
98
99
100
* 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
101
*
Jul 5, 2001
Jul 5, 2001
102
103
* 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
104
105
* 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
106
107
* 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
108
* for you, based on a few parameters. Also see the comments on
Jul 5, 2001
Jul 5, 2001
109
110
111
* 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
112
113
114
115
116
117
* 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
118
119
120
*
* 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
121
* filehandles with PhysicsFS and vice versa.
Jun 7, 2001
Jun 7, 2001
122
123
*
* Note that archives need not be named as such: if you have a ZIP file and
Jun 28, 2001
Jun 28, 2001
124
* rename it with a .PKG extension, the file will still be recognized as a
Jun 7, 2001
Jun 7, 2001
125
126
127
128
129
* 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
130
131
132
133
* - .GRP (Build Engine groupfile archives)
*
* Please see the file LICENSE in the source's root directory for licensing
* and redistribution rights.
Jun 7, 2001
Jun 7, 2001
134
*
Jun 7, 2002
Jun 7, 2002
135
136
* 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
137
*
Jun 7, 2002
Jun 7, 2002
138
* \author Ryan C. Gordon.
Jun 7, 2001
Jun 7, 2001
139
140
141
142
143
144
145
146
147
*/
#ifndef _INCLUDE_PHYSFS_H_
#define _INCLUDE_PHYSFS_H_
#ifdef __cplusplus
extern "C" {
#endif
Jun 7, 2002
Jun 7, 2002
148
#ifndef DOXYGEN_SHOULD_IGNORE_THIS
Aug 23, 2001
Aug 23, 2001
149
150
151
152
153
#if (defined _MSC_VER)
#define __EXPORT__ __declspec(dllexport)
#else
#define __EXPORT__
#endif
Jun 7, 2002
Jun 7, 2002
154
#endif /* DOXYGEN_SHOULD_IGNORE_THIS */
Aug 23, 2001
Aug 23, 2001
155
Jun 7, 2002
Jun 7, 2002
156
157
158
159
/**
* \typedef PHYSFS_uint8
* \brief An unsigned, 8-bit integer type.
*/
Mar 24, 2002
Mar 24, 2002
160
typedef unsigned char PHYSFS_uint8;
Jun 7, 2002
Jun 7, 2002
161
162
163
164
165
/**
* \typedef PHYSFS_sint8
* \brief A signed, 8-bit integer type.
*/
Mar 24, 2002
Mar 24, 2002
166
typedef signed char PHYSFS_sint8;
Jun 7, 2002
Jun 7, 2002
167
168
169
170
171
/**
* \typedef PHYSFS_uint16
* \brief An unsigned, 16-bit integer type.
*/
Mar 24, 2002
Mar 24, 2002
172
typedef unsigned short PHYSFS_uint16;
Jun 7, 2002
Jun 7, 2002
173
174
175
176
177
/**
* \typedef PHYSFS_sint16
* \brief A signed, 16-bit integer type.
*/
Mar 24, 2002
Mar 24, 2002
178
typedef signed short PHYSFS_sint16;
Jun 7, 2002
Jun 7, 2002
179
180
181
182
183
/**
* \typedef PHYSFS_uint32
* \brief An unsigned, 32-bit integer type.
*/
Mar 24, 2002
Mar 24, 2002
184
typedef unsigned int PHYSFS_uint32;
Jun 7, 2002
Jun 7, 2002
185
186
187
188
189
/**
* \typedef PHYSFS_sint32
* \brief A signed, 32-bit integer type.
*/
Mar 24, 2002
Mar 24, 2002
190
191
typedef signed int PHYSFS_sint32;
Jun 7, 2002
Jun 7, 2002
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
/**
* \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
207
#if (defined PHYSFS_NO_64BIT_SUPPORT) /* oh well. */
Mar 24, 2002
Mar 24, 2002
208
209
typedef PHYSFS_uint32 PHYSFS_uint64;
typedef PHYSFS_sint32 PHYSFS_sint64;
Apr 12, 2002
Apr 12, 2002
210
211
212
#elif (defined _MSC_VER)
typedef signed __int64 PHYSFS_sint64;
typedef unsigned __int64 PHYSFS_uint64;
Mar 24, 2002
Mar 24, 2002
213
214
215
216
217
#else
typedef unsigned long long PHYSFS_uint64;
typedef signed long long PHYSFS_sint64;
#endif
Jun 7, 2002
Jun 7, 2002
218
219
#ifndef DOXYGEN_SHOULD_IGNORE_THIS
Mar 24, 2002
Mar 24, 2002
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
/* 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
238
#endif /* DOXYGEN_SHOULD_IGNORE_THIS */
Mar 24, 2002
Mar 24, 2002
239
240
Jun 7, 2002
Jun 7, 2002
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
/**
* \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
261
262
* \sa PHYSFS_setBuffer
* \sa PHYSFS_flush
Jun 7, 2002
Jun 7, 2002
263
264
*/
typedef struct
Jun 28, 2001
Jun 28, 2001
265
{
Jun 7, 2002
Jun 7, 2002
266
void *opaque; /**< That's all you get. Don't touch. */
Jun 28, 2001
Jun 28, 2001
267
268
269
270
} PHYSFS_file;
Jun 7, 2002
Jun 7, 2002
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
/**
* \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
293
Dec 1, 2002
Dec 1, 2002
294
Jun 7, 2002
Jun 7, 2002
295
296
297
298
299
300
301
302
303
304
305
306
307
308
/**
* \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
309
{
Jun 7, 2002
Jun 7, 2002
310
311
312
PHYSFS_uint8 major; /**< major revision */
PHYSFS_uint8 minor; /**< minor revision */
PHYSFS_uint8 patch; /**< patchlevel */
Jul 5, 2001
Jul 5, 2001
313
314
} PHYSFS_Version;
Jun 7, 2002
Jun 7, 2002
315
#ifndef DOXYGEN_SHOULD_IGNORE_THIS
Jul 5, 2001
Jul 5, 2001
316
317
#define PHYSFS_VER_MAJOR 0
#define PHYSFS_VER_MINOR 1
Jan 4, 2003
Jan 4, 2003
318
#define PHYSFS_VER_PATCH 8
Jun 7, 2002
Jun 7, 2002
319
320
#endif /* DOXYGEN_SHOULD_IGNORE_THIS */
Dec 1, 2002
Dec 1, 2002
321
322
323
/* PhysicsFS state stuff ... */
Jun 7, 2002
Jun 7, 2002
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
/**
* \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
346
347
348
/**
Jun 7, 2002
Jun 7, 2002
349
350
351
352
353
* \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
354
355
356
357
*
* This is a real function; the macro PHYSFS_VERSION tells you what version
* of PhysFS you compiled against:
*
Jun 7, 2002
Jun 7, 2002
358
* \code
Jul 5, 2001
Jul 5, 2001
359
360
361
362
363
364
365
366
367
* 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
368
* \endcode
Jul 5, 2001
Jul 5, 2001
369
370
*
* This function may be called safely at any time, even before PHYSFS_init().
Jun 7, 2002
Jun 7, 2002
371
372
*
* \sa PHYSFS_VERSION
Jul 5, 2001
Jul 5, 2001
373
*/
Aug 23, 2001
Aug 23, 2001
374
__EXPORT__ void PHYSFS_getLinkedVersion(PHYSFS_Version *ver);
Jul 5, 2001
Jul 5, 2001
375
376
Jun 7, 2001
Jun 7, 2001
377
/**
Jun 7, 2002
Jun 7, 2002
378
379
380
381
* \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
382
*
Jul 8, 2001
Jul 8, 2001
383
384
385
* This should be called prior to any attempts to change your process's
* current working directory.
*
Jun 7, 2002
Jun 7, 2002
386
387
388
389
390
391
* \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
392
* gleaned from PHYSFS_getLastError().
Jun 7, 2002
Jun 7, 2002
393
394
*
* \sa PHYSFS_deinit
Jun 7, 2001
Jun 7, 2001
395
*/
Aug 23, 2001
Aug 23, 2001
396
__EXPORT__ int PHYSFS_init(const char *argv0);
Jun 7, 2001
Jun 7, 2001
397
398
399
/**
Jun 7, 2002
Jun 7, 2002
400
401
402
403
404
* \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
405
*
Jul 7, 2001
Jul 7, 2001
406
407
408
409
410
411
* 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
412
*
Jul 7, 2001
Jul 7, 2001
413
414
415
* 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
416
*
Jun 7, 2002
Jun 7, 2002
417
* \return nonzero on success, zero on error. Specifics of the error can be
Jun 7, 2001
Jun 7, 2001
418
419
* gleaned from PHYSFS_getLastError(). If failure, state of PhysFS is
* undefined, and probably badly screwed up.
Jun 7, 2002
Jun 7, 2002
420
421
*
* \sa PHYSFS_init
Jun 7, 2001
Jun 7, 2001
422
*/
Aug 23, 2001
Aug 23, 2001
423
__EXPORT__ int PHYSFS_deinit(void);
Jun 7, 2001
Jun 7, 2001
424
Jun 7, 2001
Jun 7, 2001
425
Jun 28, 2001
Jun 28, 2001
426
/**
Jun 7, 2002
Jun 7, 2002
427
428
429
* \fn const PHYSFS_ArchiveInfo **PHYSFS_supportedArchiveTypes(void)
* \brief Get a list of supported archive types.
*
Jun 28, 2001
Jun 28, 2001
430
431
432
433
434
435
* 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
436
437
* 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
438
*
Jun 7, 2002
Jun 7, 2002
439
* \code
Jun 28, 2001
Jun 28, 2001
440
441
442
443
444
445
446
* 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
447
* \endcode
Jun 28, 2001
Jun 28, 2001
448
449
450
451
*
* The return values are pointers to static internal memory, and should
* be considered READ ONLY, and never freed.
*
Jun 7, 2002
Jun 7, 2002
452
* \return READ ONLY Null-terminated array of READ ONLY structures.
Jun 28, 2001
Jun 28, 2001
453
*/
Aug 23, 2001
Aug 23, 2001
454
__EXPORT__ const PHYSFS_ArchiveInfo **PHYSFS_supportedArchiveTypes(void);
Jun 28, 2001
Jun 28, 2001
455
456
457
/**
Jun 7, 2002
Jun 7, 2002
458
459
460
* \fn void PHYSFS_freeList(void *listVar)
* \brief Deallocate resources of lists returned by PhysicsFS.
*
Jun 28, 2001
Jun 28, 2001
461
462
463
* Certain PhysicsFS functions return lists of information that are
* dynamically allocated. Use this function to free those resources.
*
Jun 7, 2002
Jun 7, 2002
464
465
466
467
468
* \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
469
*/
Mar 21, 2002
Mar 21, 2002
470
__EXPORT__ void PHYSFS_freeList(void *listVar);
Jun 28, 2001
Jun 28, 2001
471
472
Jun 7, 2001
Jun 7, 2001
473
/**
Jun 7, 2002
Jun 7, 2002
474
475
476
* \fn const char *PHYSFS_getLastError(void)
* \brief Get human-readable error information.
*
Jun 7, 2001
Jun 7, 2001
477
478
* 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
479
480
481
482
483
* 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
484
*
Jun 7, 2002
Jun 7, 2002
485
* \return READ ONLY string of last error message.
Jun 7, 2001
Jun 7, 2001
486
*/
Aug 23, 2001
Aug 23, 2001
487
__EXPORT__ const char *PHYSFS_getLastError(void);
Jun 7, 2001
Jun 7, 2001
488
489
490
/**
Jun 7, 2002
Jun 7, 2002
491
492
* \fn const char *PHYSFS_getDirSeparator(void)
* \brief Get platform-dependent dir separator string.
Jun 7, 2001
Jun 7, 2001
493
*
Jun 7, 2002
Jun 7, 2002
494
495
496
497
498
499
500
501
* 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
502
*/
Aug 23, 2001
Aug 23, 2001
503
__EXPORT__ const char *PHYSFS_getDirSeparator(void);
Jun 7, 2001
Jun 7, 2001
504
505
Jul 7, 2001
Jul 7, 2001
506
/**
Jun 7, 2002
Jun 7, 2002
507
508
509
510
511
512
* \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
513
514
515
516
517
518
519
520
521
522
523
524
*
* 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
525
526
527
528
* 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
529
530
* 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
531
*
Jun 7, 2002
Jun 7, 2002
532
* \param allow nonzero to permit symlinks, zero to deny linking.
Jul 7, 2001
Jul 7, 2001
533
*/
Aug 23, 2001
Aug 23, 2001
534
__EXPORT__ void PHYSFS_permitSymbolicLinks(int allow);
Jul 7, 2001
Jul 7, 2001
535
536
Jun 7, 2001
Jun 7, 2001
537
/**
Jun 7, 2002
Jun 7, 2002
538
539
* \fn char **PHYSFS_getCdRomDirs(void)
* \brief Get an array of paths to available CD-ROM drives.
Jun 7, 2001
Jun 7, 2001
540
*
Jul 5, 2001
Jul 5, 2001
541
542
* 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
543
544
545
546
547
548
549
550
551
* 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
552
* \code
Jul 6, 2001
Jul 6, 2001
553
* char **cds = PHYSFS_getCdRomDirs();
Jun 7, 2001
Jun 7, 2001
554
555
* char **i;
*
Jul 6, 2001
Jul 6, 2001
556
* for (i = cds; *i != NULL; i++)
Jul 5, 2001
Jul 5, 2001
557
* printf("cdrom dir [%s] is available.\n", *i);
Jun 7, 2001
Jun 7, 2001
558
*
Jul 6, 2001
Jul 6, 2001
559
* PHYSFS_freeList(cds);
Jun 7, 2002
Jun 7, 2002
560
* \endcode
Jul 6, 2001
Jul 6, 2001
561
*
Jun 7, 2001
Jun 7, 2001
562
563
* This call may block while drives spin up. Be forewarned.
*
Jun 28, 2001
Jun 28, 2001
564
565
566
* 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
567
* \return Null-terminated array of null-terminated strings.
Jun 7, 2001
Jun 7, 2001
568
*/
Aug 23, 2001
Aug 23, 2001
569
__EXPORT__ char **PHYSFS_getCdRomDirs(void);
Jun 7, 2001
Jun 7, 2001
570
571
572
/**
Jun 7, 2002
Jun 7, 2002
573
574
575
* \fn const char *PHYSFS_getBaseDir(void)
* \brief Get the path where the application resides.
*
Jun 7, 2001
Jun 7, 2001
576
577
* Helper function.
*
Jul 5, 2001
Jul 5, 2001
578
* Get the "base dir". This is the directory where the application was run
Jun 28, 2001
Jun 28, 2001
579
580
* 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
581
*
Jul 5, 2001
Jul 5, 2001
582
* You should probably use the base dir in your search path.
Jun 7, 2001
Jun 7, 2001
583
*
Jun 7, 2002
Jun 7, 2002
584
585
586
* \return READ ONLY string of base dir in platform-dependent notation.
*
* \sa PHYSFS_getUserDir
Jun 7, 2001
Jun 7, 2001
587
*/
Aug 23, 2001
Aug 23, 2001
588
__EXPORT__ const char *PHYSFS_getBaseDir(void);
Jun 7, 2001
Jun 7, 2001
589
590
591
/**
Jun 7, 2002
Jun 7, 2002
592
593
594
* \fn const char *PHYSFS_getUserDir(void)
* \brief Get the path where user's home directory resides.
*
Jun 7, 2001
Jun 7, 2001
595
596
* Helper function.
*
Jul 5, 2001
Jul 5, 2001
597
* Get the "user dir". This is meant to be a suggestion of where a specific
Jun 7, 2001
Jun 7, 2001
598
* user of the system can store files. On Unix, this is her home directory.
Jun 28, 2001
Jun 28, 2001
599
* On systems with no concept of multiple home directories (MacOS, win95),
Jul 5, 2001
Jul 5, 2001
600
* this will default to something like "C:\mybasedir\users\username"
Jun 28, 2001
Jun 28, 2001
601
602
* 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
603
*
Jul 5, 2001
Jul 5, 2001
604
* You should probably use the user dir as the basis for your write dir, and
Jun 7, 2001
Jun 7, 2001
605
606
* also put it near the beginning of your search path.
*
Jun 7, 2002
Jun 7, 2002
607
608
609
* \return READ ONLY string of user dir in platform-dependent notation.
*
* \sa PHYSFS_getBaseDir
Jun 7, 2001
Jun 7, 2001
610
*/
Aug 23, 2001
Aug 23, 2001
611
__EXPORT__ const char *PHYSFS_getUserDir(void);
Jun 7, 2001
Jun 7, 2001
612
613
614
/**
Jun 7, 2002
Jun 7, 2002
615
616
617
* \fn const char *PHYSFS_getWriteDir(void)
* \brief Get path where PhysicsFS will allow file writing.
*
Jul 5, 2001
Jul 5, 2001
618
* Get the current write dir. The default write dir is NULL.
Jun 7, 2001
Jun 7, 2001
619
*
Jun 7, 2002
Jun 7, 2002
620
* \return READ ONLY string of write dir in platform-dependent notation,
Jun 7, 2001
Jun 7, 2001
621
* OR NULL IF NO WRITE PATH IS CURRENTLY SET.
Jun 7, 2002
Jun 7, 2002
622
623
*
* \sa PHYSFS_setWriteDir
Jun 7, 2001
Jun 7, 2001
624
*/
Aug 23, 2001
Aug 23, 2001
625
__EXPORT__ const char *PHYSFS_getWriteDir(void);
Jun 7, 2001
Jun 7, 2001
626
627
628
/**
Jun 7, 2002
Jun 7, 2002
629
630
631
* \fn int PHYSFS_setWriteDir(const char *newDir)
* \brief Tell PhysicsFS where it may write files.
*
Jul 5, 2001
Jul 5, 2001
632
* Set a new write dir. This will override the previous setting. If the
Jun 7, 2001
Jun 7, 2001
633
634
635
* 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
636
637
* 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
638
*
Jun 7, 2002
Jun 7, 2002
639
* \param newDir The new directory to be the root of the write dir,
Jun 28, 2001
Jun 28, 2001
640
* specified in platform-dependent notation. Setting to NULL
Jul 5, 2001
Jul 5, 2001
641
* disables the write dir, so no files can be opened for
Jun 7, 2001
Jun 7, 2001
642
* writing via PhysicsFS.
Jun 7, 2002
Jun 7, 2002
643
* \return non-zero on success, zero on failure. All attempts to open a file
Jun 7, 2001
Jun 7, 2001
644
645
646
* 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
647
* \sa PHYSFS_getWriteDir
Jun 7, 2001
Jun 7, 2001
648
*/
Aug 23, 2001
Aug 23, 2001
649
__EXPORT__ int PHYSFS_setWriteDir(const char *newDir);
Jun 7, 2001
Jun 7, 2001
650
651
652
/**
Jun 7, 2002
Jun 7, 2002
653
654
655
656
657
* \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
658
*
Jun 7, 2002
Jun 7, 2002
659
* \param newDir directory or archive to add to the path, in
Jun 7, 2001
Jun 7, 2001
660
* platform-dependent notation.
Jun 7, 2002
Jun 7, 2002
661
662
* \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
663
664
* missing, etc). Specifics of the error can be
* gleaned from PHYSFS_getLastError().
Jun 7, 2002
Jun 7, 2002
665
666
667
*
* \sa PHYSFS_removeFromSearchPath
* \sa PHYSFS_getSearchPath
Jun 7, 2001
Jun 7, 2001
668
*/
Aug 23, 2001
Aug 23, 2001
669
__EXPORT__ int PHYSFS_addToSearchPath(const char *newDir, int appendToPath);
Jun 7, 2001
Jun 7, 2001
670
671
672
/**
Jun 7, 2002
Jun 7, 2002
673
674
* \fn int PHYSFS_removeFromSearchPath(const char *oldDir)
* \brief Remove a directory or archive from the search path.
Jun 7, 2001
Jun 7, 2001
675
676
677
678
679
680
681
*
* 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
682
683
* \param oldDir dir/archive to remove.
* \return nonzero on success, zero on failure.
Jun 7, 2001
Jun 7, 2001
684
* Specifics of the error can be gleaned from PHYSFS_getLastError().
Jun 7, 2002
Jun 7, 2002
685
686
687
*
* \sa PHYSFS_addToSearchPath
* \sa PHYSFS_getSearchPath
Jun 7, 2001
Jun 7, 2001
688
*/
Aug 23, 2001
Aug 23, 2001
689
__EXPORT__ int PHYSFS_removeFromSearchPath(const char *oldDir);
Jun 7, 2001
Jun 7, 2001
690
691
692
/**
Jun 7, 2002
Jun 7, 2002
693
694
695
696
* \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
697
698
699
700
*
* 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
701
* \code
Jun 7, 2001
Jun 7, 2001
702
703
704
705
* char **i;
*
* for (i = PHYSFS_getSearchPath(); *i != NULL; i++)
* printf("[%s] is in the search path.\n", *i);
Jun 7, 2002
Jun 7, 2002
706
* \endcode
Jun 7, 2001
Jun 7, 2001
707
*
Jun 28, 2001
Jun 28, 2001
708
709
* 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
710
*
Jun 7, 2002
Jun 7, 2002
711
* \return Null-terminated array of null-terminated strings. NULL if there
Jul 5, 2001
Jul 5, 2001
712
* was a problem (read: OUT OF MEMORY).
Jun 7, 2002
Jun 7, 2002
713
714
715
*
* \sa PHYSFS_addToSearchPath
* \sa PHYSFS_removeFromSearchPath
Jun 7, 2001
Jun 7, 2001
716
*/
Aug 23, 2001
Aug 23, 2001
717
__EXPORT__ char **PHYSFS_getSearchPath(void);
Jun 7, 2001
Jun 7, 2001
718
719
720
/**
Jun 7, 2002
Jun 7, 2002
721
722
723
* \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
724
725
* Helper function.
*
Jun 7, 2002
Jun 7, 2002
726
727
* The write dir will be set to "userdir/.organization/appName", which is
* created if it doesn't exist.
Jun 7, 2001
Jun 7, 2001
728
729
730
731
732
733
734
*
* 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
735
736
737
* - 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
738
739
740
741
742
743
744
745
746
*
* 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
747
* all for you. Feel free to add more to the search path manually, too.
Jun 7, 2001
Jun 7, 2001
748
*
Jun 7, 2002
Jun 7, 2002
749
* \param organization Name of your company/group/etc to be used as a
Sep 26, 2001
Sep 26, 2001
750
751
* dirname, so keep it small, and no-frills.
*
Jun 7, 2002
Jun 7, 2002
752
* \param appName Program-specific name of your program, to separate it
Jun 7, 2001
Jun 7, 2001
753
754
* from other programs using PhysicsFS.
*
Jul 26, 2002
Jul 26, 2002
755
* \param archiveExt File extension used by your program to specify an
Jun 7, 2001
Jun 7, 2001
756
757
* 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
758
759
760
* 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
761
*
Jun 7, 2002
Jun 7, 2002
762
* \param includeCdRoms Non-zero to include CD-ROMs in the search path, and
Jun 7, 2001
Jun 7, 2001
763
764
765
766
767
768
769
* (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
770
*
Jun 7, 2002
Jun 7, 2002
771
* \param archivesFirst Non-zero to prepend the archives to the search path.
Jun 7, 2001
Jun 7, 2001
772
* Zero to append them. Ignored if !(archiveExt).
Sep 26, 2001
Sep 26, 2001
773
*
Jun 7, 2002
Jun 7, 2002
774
* \return nonzero on success, zero on error. Specifics of the error can be
Jul 6, 2001
Jul 6, 2001
775
* gleaned from PHYSFS_getLastError().
Jun 7, 2001
Jun 7, 2001
776
*/
Sep 26, 2001
Sep 26, 2001
777
778
__EXPORT__ int PHYSFS_setSaneConfig(const char *organization,
const char *appName,
Aug 23, 2001
Aug 23, 2001
779
780
781
const char *archiveExt,
int includeCdRoms,
int archivesFirst);
Jun 7, 2001
Jun 7, 2001
782
783
Dec 1, 2002
Dec 1, 2002
784
785
/* Directory management stuff ... */
Jun 7, 2001
Jun 7, 2001
786
/**
Jun 7, 2002
Jun 7, 2002
787
788
789
790
791
792
* \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
793
*
Jul 5, 2001
Jul 5, 2001
794
* So if you've got the write dir set to "C:\mygame\writedir" and call
Jun 7, 2001
Jun 7, 2001
795
* PHYSFS_mkdir("downloads/maps") then the directories
Jul 5, 2001
Jul 5, 2001
796
* "C:\mygame\writedir\downloads" and "C:\mygame\writedir\downloads\maps"
Jun 28, 2001
Jun 28, 2001
797
798
799
* 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
800
*
Jun 7, 2002
Jun 7, 2002
801
802
* \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
803
* gleaned from PHYSFS_getLastError().
Jun 7, 2002
Jun 7, 2002
804
805
*
* \sa PHYSFS_delete
Jun 7, 2001
Jun 7, 2001
806
*/
Aug 23, 2001
Aug 23, 2001
807
__EXPORT__ int PHYSFS_mkdir(const char *dirName);
Jun 7, 2001
Jun 7, 2001
808
809
810
/**
Jun 7, 2002
Jun 7, 2002
811
812
813
814
815
* \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
816
*
Jun 28, 2001
Jun 28, 2001
817
* A directory must be empty before this call can delete it.
Jun 7, 2001
Jun 7, 2001
818
*
Mar 25, 2002
Mar 25, 2002
819
820
821
* 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
822
* So if you've got the write dir set to "C:\mygame\writedir" and call
Jun 7, 2001
Jun 7, 2001
823
* PHYSFS_delete("downloads/maps/level1.map") then the file
Jul 5, 2001
Jul 5, 2001
824
* "C:\mygame\writedir\downloads\maps\level1.map" is removed from the
Jun 7, 2001
Jun 7, 2001
825
826
827
* physical filesystem, if it exists and the operating system permits the
* deletion.
*
Jun 7, 2001
Jun 7, 2001
828
829
830
831
* 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
832
833
834
835
* 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
836
837
* \param filename Filename to delete.
* \return nonzero on success, zero on error. Specifics of the error can be
Jun 7, 2001
Jun 7, 2001
838
839
* gleaned from PHYSFS_getLastError().
*/
Aug 23, 2001
Aug 23, 2001
840
__EXPORT__ int PHYSFS_delete(const char *filename);
Jun 7, 2001
Jun 7, 2001
841
842
843
/**
Jun 7, 2002
Jun 7, 2002
844
845
846
847
848
849
850
851
* \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
852
853
*
* So, if you look for "maps/level1.map", and C:\mygame is in your search
Jun 28, 2001
Jun 28, 2001
854
* path and C:\mygame\maps\level1.map exists, then "C:\mygame" is returned.
Jun 7, 2001
Jun 7, 2001
855
*
Jul 7, 2001
Jul 7, 2001
856
857
858
* 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
859
*
Jun 7, 2002
Jun 7, 2002
860
861
* \param filename file to look for.
* \return READ ONLY string of element of search path containing the
Jun 28, 2001
Jun 28, 2001
862
863
* the file in question. NULL if not found.
*/
Aug 23, 2001
Aug 23, 2001
864
__EXPORT__ const char *PHYSFS_getRealDir(const char *filename);
Jun 28, 2001
Jun 28, 2001
865
866
867
/**
Jun 7, 2002
Jun 7, 2002
868
869
870
871
872
873
874
* \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
875
*
Jun 7, 2002
Jun 7, 2002
876
* \code
Jun 28, 2001
Jun 28, 2001
877
878
879
880
* char **rc = PHYSFS_enumerateFiles("savegames");
* char **i;
*
* for (i = rc; *i != NULL; i++)
Jun 7, 2002
Jun 7, 2002
881
* printf(" * We've got [%s].\n", *i);
Jun 28, 2001
Jun 28, 2001
882
883
*
* PHYSFS_freeList(rc);
Jun 7, 2002
Jun 7, 2002
884
* \endcode
Jun 28, 2001
Jun 28, 2001
885
886
887
*
* ...will print:
*
Jun 7, 2002
Jun 7, 2002
888
* \verbatim
Jun 28, 2001
Jun 28, 2001
889
890
891
* We've got [x.sav].
* We've got [y.sav].
* We've got [z.sav].
Jun 7, 2002
Jun 7, 2002
892
* We've got [w.sav].\endverbatim
Jun 28, 2001
Jun 28, 2001
893
*
Jul 5, 2001
Jul 5, 2001
894
895
896
* 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
897
898
899
* 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
900
901
* \param dir directory in platform-independent notation to enumerate.
* \return Null-terminated array of null-terminated strings.
Jun 7, 2001
Jun 7, 2001
902
*/
Aug 23, 2001
Aug 23, 2001
903
__EXPORT__ char **PHYSFS_enumerateFiles(const char *dir);
Jun 7, 2001
Jun 7, 2001
904
905
Jul 7, 2001
Jul 7, 2001
906
/**
Jun 7, 2002
Jun 7, 2002
907
908
909
910
* \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
911
912
913
914
915
916
* 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
917
918
919
920
921
* \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
922
*/
Aug 23, 2001
Aug 23, 2001
923
__EXPORT__ int PHYSFS_exists(const char *fname);
Jul 7, 2001
Jul 7, 2001
924
925
926
/**
Jun 7, 2002
Jun 7, 2002
927
928
929
* \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
930
931
932
933
934
935
936
* 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
937
938
939
940
941
* \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
942
*/
Aug 23, 2001
Aug 23, 2001
943
__EXPORT__ int PHYSFS_isDirectory(const char *fname);
Jul 7, 2001
Jul 7, 2001
944
945
946
/**
Jun 7, 2002
Jun 7, 2002
947
948
949
* \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
950
951
952
953
954
955
956
* 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
957
958
959
960
961
* \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
962
*/
Aug 23, 2001
Aug 23, 2001
963
__EXPORT__ int PHYSFS_isSymbolicLink(const char *fname);
Jul 7, 2001
Jul 7, 2001
964
965
Dec 1, 2002
Dec 1, 2002
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
/**
* \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
984
/**
Jun 7, 2002
Jun 7, 2002
985
986
987
* \fn PHYSFS_file *PHYSFS_openWrite(const char *filename)
* \brief Open a file for writing.
*
Jun 7, 2001
Jun 7, 2001
988
* Open a file for writing, in platform-independent notation and in relation
Jul 5, 2001
Jul 5, 2001
989
* to the write dir as the root of the writable filesystem. The specified
Jun 7, 2001
Jun 7, 2001
990
991
992
* 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
993
994
995
996
* 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.
*
Jun 7, 2002
Jun 7, 2002
997
998
* \param filename File to open.
* \return A valid PhysicsFS filehandle on success, NULL on error. Specifics
Jun 7, 2001
Jun 7, 2001
999
* of the error can be gleaned from PHYSFS_getLastError().
Jun 7, 2002
Jun 7, 2002
1000
*