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