physfs.h
1
2
3
4
5
/**
* \file physfs.h
*
* Main header file for PhysicsFS.
*/
7
/**
8
9
10
* \mainpage PhysicsFS
*
* The latest version of PhysicsFS can be found at:
11
* https://icculus.org/physfs/
13
14
15
16
17
18
19
20
21
22
* 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.
*
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
29
* language from piddling over c:\\config.sys, for example. If you'd rather
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.
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
* got the following search path defined (to use a win32 example again):
*
64
65
66
67
* - C:\\mygame
* - C:\\mygame\\myuserfiles
* - D:\\mygamescdromdatafiles
* - C:\\mygame\\installeddatafiles.zip
68
*
69
* Then a call to PHYSFS_openRead("textfiles/myfile.txt") (note the directory
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
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.
79
*
80
* Files opened through PhysicsFS may NOT contain "." or ".." or ":" as dir
81
82
83
84
85
86
87
* elements. Not only are these meaningless on MacOS Classic 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. For portability, there is no mechanism for
* creating new symlinks in PhysicsFS.
88
89
90
91
92
93
*
* 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.
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
97
* platform-independence. There is a function to tell you the current
98
* platform's dir separator ("\\" on windows, "/" on Unix, ":" on MacOS),
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.
102
*
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
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
107
108
* use the base dir for both searching and writing. There is a helper
* function (PHYSFS_setSaneConfig()) that puts together a basic configuration
109
* for you, based on a few parameters. Also see the comments on
110
* PHYSFS_getBaseDir(), and PHYSFS_getPrefDir() for info on what those
111
112
* are and how they can help you determine an optimal search path.
*
113
114
115
116
117
118
119
120
121
122
123
124
* PhysicsFS 2.0 adds the concept of "mounting" archives to arbitrary points
* in the search path. If a zipfile contains "maps/level.map" and you mount
* that archive at "mods/mymod", then you would have to open
* "mods/mymod/maps/level.map" to access the file, even though "mods/mymod"
* isn't actually specified in the .zip file. Unlike the Unix mentality of
* mounting a filesystem, "mods/mymod" doesn't actually have to exist when
* mounting the zipfile. It's a "virtual" directory. The mounting mechanism
* allows the developer to seperate archives in the tree and avoid trampling
* over files when added new archives, such as including mod support in a
* game...keeping external content on a tight leash in this manner can be of
* utmost importance to some applications.
*
125
126
* PhysicsFS is mostly thread safe. The errors returned by
* PHYSFS_getLastErrorCode() are unique by thread, and library-state-setting
127
128
129
130
* 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.
131
132
*
* While you CAN use stdio/syscall file access in a program that has PHYSFS_*
133
134
135
* calls, doing so is not recommended, and you can not directly use system
* filehandles with PhysicsFS and vice versa (but as of PhysicsFS 2.1, you
* can wrap them in a PHYSFS_Io interface yourself if you wanted to).
136
137
*
* Note that archives need not be named as such: if you have a ZIP file and
138
* rename it with a .PKG extension, the file will still be recognized as a
139
* ZIP archive by PhysicsFS; the file's contents are used to determine its
140
* type where possible.
141
142
143
*
* Currently supported archive types:
* - .ZIP (pkZip/WinZip/Info-ZIP compatible)
144
145
* - .7Z (7zip archives)
* - .ISO (ISO9660 files, CD-ROM images)
146
* - .GRP (Build Engine groupfile archives)
147
* - .PAK (Quake I/II archive format)
148
* - .HOG (Descent I/II/III HOG file archives)
149
* - .MVL (Descent II movielib archives)
150
* - .WAD (DOOM engine archives)
151
* - .VDF (Gothic I/II engine archives)
152
* - .SLB (Independence War archives)
153
154
155
*
* String policy for PhysicsFS 2.0 and later:
*
156
157
158
159
160
* PhysicsFS 1.0 could only deal with null-terminated ASCII strings. All high
* ASCII chars resulted in undefined behaviour, and there was no Unicode
* support at all. PhysicsFS 2.0 supports Unicode without breaking binary
* compatibility with the 1.0 API by using UTF-8 encoding of all strings
* passed in and out of the library.
161
162
163
164
165
*
* All strings passed through PhysicsFS are in null-terminated UTF-8 format.
* This means that if all you care about is English (ASCII characters <= 127)
* then you just use regular C strings. If you care about Unicode (and you
* should!) then you need to figure out what your platform wants, needs, and
166
167
168
169
* offers. If you are on Windows before Win2000 and build with Unicode
* support, your TCHAR strings are two bytes per character (this is called
* "UCS-2 encoding"). Any modern Windows uses UTF-16, which is two bytes
* per character for most characters, but some characters are four. You
170
* should convert them to UTF-8 before handing them to PhysicsFS with
171
172
* PHYSFS_utf8FromUtf16(), which handles both UTF-16 and UCS-2. If you're
* using Unix or Mac OS X, your wchar_t strings are four bytes per character
173
174
175
176
177
178
179
180
* ("UCS-4 encoding", sometimes called "UTF-32"). Use PHYSFS_utf8FromUcs4().
* Mac OS X can give you UTF-8 directly from a CFString or NSString, and many
* Unixes generally give you C strings in UTF-8 format everywhere. If you
* have a single-byte high ASCII charset, like so-many European "codepages"
* you may be out of luck. We'll convert from "Latin1" to UTF-8 only, and
* never back to Latin1. If you're above ASCII 127, all bets are off: move
* to Unicode or use your platform's facilities. Passing a C string with
* high-ASCII data that isn't UTF-8 encoded will NOT do what you expect!
181
182
183
184
185
186
*
* Naturally, there's also PHYSFS_utf8ToUcs2(), PHYSFS_utf8ToUtf16(), and
* PHYSFS_utf8ToUcs4() to get data back into a format you like. Behind the
* scenes, PhysicsFS will use Unicode where possible: the UTF-8 strings on
* Windows will be converted and used with the multibyte Windows APIs, for
* example.
187
188
189
190
*
* PhysicsFS offers basic encoding conversion support, but not a whole string
* library. Get your stuff into whatever format you can work with.
*
191
192
193
194
195
* Most platforms supported by PhysicsFS 2.1 and later fully support Unicode.
* Some older platforms have been dropped (Windows 95, Mac OS 9). Some, like
* OS/2, might be able to convert to a local codepage or will just fail to
* open/create the file. Modern OSes (macOS, Linux, Windows, etc) should all
* be fine.
196
197
*
* Many game-specific archivers are seriously unprepared for Unicode (the
198
199
200
201
202
203
204
205
206
* Descent HOG/MVL and Build Engine GRP archivers, for example, only offer a
* DOS 8.3 filename, for example). Nothing can be done for these, but they
* tend to be legacy formats for existing content that was all ASCII (and
* thus, valid UTF-8) anyhow. Other formats, like .ZIP, don't explicitly
* offer Unicode support, but unofficially expect filenames to be UTF-8
* encoded, and thus Just Work. Most everything does the right thing without
* bothering you, but it's good to be aware of these nuances in case they
* don't.
*
207
208
209
*
* Other stuff:
*
210
* Please see the file LICENSE.txt in the source's root directory for
211
* licensing and redistribution rights.
212
*
213
214
* Please see the file CREDITS.txt in the source's "docs" directory for
* a more or less complete list of who's responsible for this.
215
*
216
* \author Ryan C. Gordon.
217
218
219
220
221
222
223
224
225
*/
#ifndef _INCLUDE_PHYSFS_H_
#define _INCLUDE_PHYSFS_H_
#ifdef __cplusplus
extern "C" {
#endif
226
227
#if defined(PHYSFS_DECL)
/* do nothing. */
228
#elif defined(_MSC_VER)
229
#define PHYSFS_DECL __declspec(dllexport)
230
#elif defined(__SUNPRO_C)
231
#define PHYSFS_DECL __global
232
#elif ((__GNUC__ >= 3) && (!defined(__EMX__)) && (!defined(sun)))
233
#define PHYSFS_DECL __attribute__((visibility("default")))
235
#define PHYSFS_DECL
238
239
240
241
242
243
244
245
#if defined(PHYSFS_DEPRECATED)
/* do nothing. */
#elif (__GNUC__ >= 4) /* technically, this arrived in gcc 3.1, but oh well. */
#define PHYSFS_DEPRECATED __attribute__((deprecated))
#else
#define PHYSFS_DEPRECATED
#endif
246
247
248
249
250
#if 0 /* !!! FIXME: look into this later. */
#if defined(PHYSFS_CALL)
/* do nothing. */
#elif defined(__WIN32__) && !defined(__GNUC__)
#define PHYSFS_CALL __cdecl
251
252
#elif defined(__OS2__) || defined(OS2) /* should work across all compilers. */
#define PHYSFS_CALL _System
253
254
255
256
257
#else
#define PHYSFS_CALL
#endif
#endif
258
259
260
261
/**
* \typedef PHYSFS_uint8
* \brief An unsigned, 8-bit integer type.
*/
262
typedef unsigned char PHYSFS_uint8;
263
264
265
266
267
/**
* \typedef PHYSFS_sint8
* \brief A signed, 8-bit integer type.
*/
268
typedef signed char PHYSFS_sint8;
269
270
271
272
273
/**
* \typedef PHYSFS_uint16
* \brief An unsigned, 16-bit integer type.
*/
274
typedef unsigned short PHYSFS_uint16;
275
276
277
278
279
/**
* \typedef PHYSFS_sint16
* \brief A signed, 16-bit integer type.
*/
280
typedef signed short PHYSFS_sint16;
281
282
283
284
285
/**
* \typedef PHYSFS_uint32
* \brief An unsigned, 32-bit integer type.
*/
286
typedef unsigned int PHYSFS_uint32;
287
288
289
290
291
/**
* \typedef PHYSFS_sint32
* \brief A signed, 32-bit integer type.
*/
292
293
typedef signed int PHYSFS_sint32;
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
/**
* \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!
*/
309
#if (defined PHYSFS_NO_64BIT_SUPPORT) /* oh well. */
310
311
typedef PHYSFS_uint32 PHYSFS_uint64;
typedef PHYSFS_sint32 PHYSFS_sint64;
312
313
314
#elif (defined _MSC_VER)
typedef signed __int64 PHYSFS_sint64;
typedef unsigned __int64 PHYSFS_uint64;
315
316
317
318
319
#else
typedef unsigned long long PHYSFS_uint64;
typedef signed long long PHYSFS_sint64;
#endif
320
321
#ifndef DOXYGEN_SHOULD_IGNORE_THIS
322
/* Make sure the types really have the right sizes */
323
324
#define PHYSFS_COMPILE_TIME_ASSERT(name, x) \
typedef int PHYSFS_compile_time_assert_##name[(x) * 2 - 1]
326
327
328
329
330
331
PHYSFS_COMPILE_TIME_ASSERT(uint8IsOneByte, sizeof(PHYSFS_uint8) == 1);
PHYSFS_COMPILE_TIME_ASSERT(sint8IsOneByte, sizeof(PHYSFS_sint8) == 1);
PHYSFS_COMPILE_TIME_ASSERT(uint16IsTwoBytes, sizeof(PHYSFS_uint16) == 2);
PHYSFS_COMPILE_TIME_ASSERT(sint16IsTwoBytes, sizeof(PHYSFS_sint16) == 2);
PHYSFS_COMPILE_TIME_ASSERT(uint32IsFourBytes, sizeof(PHYSFS_uint32) == 4);
PHYSFS_COMPILE_TIME_ASSERT(sint32IsFourBytes, sizeof(PHYSFS_sint32) == 4);
332
333
#ifndef PHYSFS_NO_64BIT_SUPPORT
334
335
PHYSFS_COMPILE_TIME_ASSERT(uint64IsEightBytes, sizeof(PHYSFS_uint64) == 8);
PHYSFS_COMPILE_TIME_ASSERT(sint64IsEightBytes, sizeof(PHYSFS_sint64) == 8);
336
337
338
339
#endif
#undef PHYSFS_COMPILE_TIME_ASSERT
340
#endif /* DOXYGEN_SHOULD_IGNORE_THIS */
344
* \struct PHYSFS_File
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
* \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
363
364
* \sa PHYSFS_setBuffer
* \sa PHYSFS_flush
366
typedef struct PHYSFS_File
368
void *opaque; /**< That's all you get. Don't touch. */
369
} PHYSFS_File;
371
372
373
374
375
376
377
378
379
380
381
382
383
/**
* \def PHYSFS_file
* \brief 1.0 API compatibility define.
*
* PHYSFS_file is identical to PHYSFS_File. This #define is here for backwards
* compatibility with the 1.0 API, which had an inconsistent capitalization
* convention in this case. New code should use PHYSFS_File, as this #define
* may go away someday.
*
* \sa PHYSFS_File
*/
#define PHYSFS_file PHYSFS_File
386
387
388
389
390
391
392
393
394
395
396
397
398
399
/**
* \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
400
401
* \sa PHYSFS_registerArchiver
* \sa PHYSFS_deregisterArchiver
403
typedef struct PHYSFS_ArchiveInfo
404
405
406
407
408
{
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 */
409
int supportsSymlinks; /**< non-zero if archive offers symbolic links. */
410
} PHYSFS_ArchiveInfo;
413
414
415
416
417
418
419
420
421
422
423
/**
* \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
424
* \sa PHYSFS_getLinkedVersion
426
typedef struct PHYSFS_Version
428
429
430
PHYSFS_uint8 major; /**< major revision */
PHYSFS_uint8 minor; /**< minor revision */
PHYSFS_uint8 patch; /**< patchlevel */
431
432
} PHYSFS_Version;
434
#ifndef DOXYGEN_SHOULD_IGNORE_THIS
435
#define PHYSFS_VER_MAJOR 3
436
#define PHYSFS_VER_MINOR 1
437
#define PHYSFS_VER_PATCH 0
438
439
#endif /* DOXYGEN_SHOULD_IGNORE_THIS */
440
441
442
/* PhysicsFS state stuff ... */
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
/**
* \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; \
}
465
466
467
/**
468
469
470
471
472
* \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.
473
474
475
476
*
* This is a real function; the macro PHYSFS_VERSION tells you what version
* of PhysFS you compiled against:
*
478
479
480
481
482
483
484
485
486
* 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);
487
* \endcode
488
489
*
* This function may be called safely at any time, even before PHYSFS_init().
490
491
*
* \sa PHYSFS_VERSION
493
PHYSFS_DECL void PHYSFS_getLinkedVersion(PHYSFS_Version *ver);
496
497
498
499
500
501
502
503
#ifdef __ANDROID__
typedef struct PHYSFS_AndroidInit
{
void *jnienv;
void *context;
} PHYSFS_AndroidInit;
#endif
505
506
507
508
* \fn int PHYSFS_init(const char *argv0)
* \brief Initialize the PhysicsFS library.
*
* This must be called before any other PhysicsFS function.
510
511
512
* This should be called prior to any attempts to change your process's
* current working directory.
*
513
514
515
516
517
518
519
520
521
522
523
* \warning On Android, argv0 should be a non-NULL pointer to a
* PHYSFS_AndroidInit struct. This struct must hold a valid JNIEnv *
* and a JNI jobject of a Context (either the application context or
* the current Activity is fine). Both are cast to a void * so we
* don't need jni.h included wherever physfs.h is. PhysicsFS
* uses these objects to query some system details. PhysicsFS does
* not hold a reference to the JNIEnv or Context past the call to
* PHYSFS_init(). If you pass a NULL here, PHYSFS_init can still
* succeed, but PHYSFS_getBaseDir() and PHYSFS_getPrefDir() will be
* incorrect.
*
524
525
526
* \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
527
528
* something in here. Many Unix-like systems _need_ to pass argv[0]
* from main() in here. See warning about Android, too!
529
* \return nonzero on success, zero on error. Specifics of the error can be
530
* gleaned from PHYSFS_getLastError().
531
532
*
* \sa PHYSFS_deinit
533
* \sa PHYSFS_isInit
535
PHYSFS_DECL int PHYSFS_init(const char *argv0);
539
540
541
542
543
* \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.
545
546
547
548
549
550
* 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.
552
* Once successfully deinitialized, PHYSFS_init() can be called again to
553
554
555
* restart the subsystem. All default API states are restored at this
* point, with the exception of any custom allocator you might have
* specified, which survives between initializations.
557
* \return nonzero on success, zero on error. Specifics of the error can be
558
559
* gleaned from PHYSFS_getLastError(). If failure, state of PhysFS is
* undefined, and probably badly screwed up.
560
561
*
* \sa PHYSFS_init
562
* \sa PHYSFS_isInit
564
PHYSFS_DECL int PHYSFS_deinit(void);
568
569
570
* \fn const PHYSFS_ArchiveInfo **PHYSFS_supportedArchiveTypes(void)
* \brief Get a list of supported archive types.
*
571
572
573
574
575
576
* 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.
*
577
578
* The returned value is an array of pointers to PHYSFS_ArchiveInfo structures,
* with a NULL entry to signify the end of the list:
581
582
583
584
585
* PHYSFS_ArchiveInfo **i;
*
* for (i = PHYSFS_supportedArchiveTypes(); *i != NULL; i++)
* {
* printf("Supported archive: [%s], which is [%s].\n",
586
* (*i)->extension, (*i)->description);
588
* \endcode
590
591
* The return values are pointers to internal memory, and should
* be considered READ ONLY, and never freed. The returned values are
592
593
* valid until the next call to PHYSFS_deinit(), PHYSFS_registerArchiver(),
* or PHYSFS_deregisterArchiver().
595
* \return READ ONLY Null-terminated array of READ ONLY structures.
596
597
598
*
* \sa PHYSFS_registerArchiver
* \sa PHYSFS_deregisterArchiver
600
PHYSFS_DECL const PHYSFS_ArchiveInfo **PHYSFS_supportedArchiveTypes(void);
601
602
603
/**
604
605
606
* \fn void PHYSFS_freeList(void *listVar)
* \brief Deallocate resources of lists returned by PhysicsFS.
*
607
608
609
* Certain PhysicsFS functions return lists of information that are
* dynamically allocated. Use this function to free those resources.
*
610
611
612
* It is safe to pass a NULL here, but doing so will cause a crash in versions
* before PhysicsFS 2.1.0.
*
613
* \param listVar List of information specified as freeable by this function.
614
* Passing NULL is safe; it is a valid no-op.
615
616
617
618
*
* \sa PHYSFS_getCdRomDirs
* \sa PHYSFS_enumerateFiles
* \sa PHYSFS_getSearchPath
620
PHYSFS_DECL void PHYSFS_freeList(void *listVar);
623
/**
624
625
626
* \fn const char *PHYSFS_getLastError(void)
* \brief Get human-readable error information.
*
627
628
* \deprecated Use PHYSFS_getLastErrorCode() and PHYSFS_getErrorByCode() instead.
*
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
* \warning As of PhysicsFS 2.1, this function has been nerfed.
* Before PhysicsFS 2.1, this function was the only way to get
* error details beyond a given function's basic return value.
* This was meant to be a human-readable string in one of several
* languages, and was not useful for application parsing. This was
* a problem, because the developer and not the user chose the
* language at compile time, and the PhysicsFS maintainers had
* to (poorly) maintain a significant amount of localization work.
* The app couldn't parse the strings, even if they counted on a
* specific language, since some were dynamically generated.
* In 2.1 and later, this always returns a static string in
* English; you may use it as a key string for your own
* localizations if you like, as we'll promise not to change
* existing error strings. Also, if your application wants to
* look at specific errors, we now offer a better option:
* use PHYSFS_getLastErrorCode() instead.
*
646
* Get the last PhysicsFS error message as a human-readable, null-terminated
647
648
* string. This will return NULL if there's been no error since the last call
* to this function. The pointer returned by this call points to an internal
649
650
651
652
653
* 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().
*
654
655
656
657
658
659
660
661
662
663
664
665
666
* PHYSFS_getLastError() and PHYSFS_getLastErrorCode() both reset the same
* thread-specific error state. Calling one will wipe out the other's
* data. If you need both, call PHYSFS_getLastErrorCode(), then pass that
* value to PHYSFS_getErrorByCode().
*
* As of PhysicsFS 2.1, this function only presents text in the English
* language, but the strings are static, so you can use them as keys into
* your own localization dictionary. These strings are meant to be passed on
* directly to the user.
*
* Generally, applications should only concern themselves with whether a
* given function failed; however, if your code require more specifics, you
* should use PHYSFS_getLastErrorCode() instead of this function.
667
*
668
* \return READ ONLY string of last error message.
669
670
671
*
* \sa PHYSFS_getLastErrorCode
* \sa PHYSFS_getErrorByCode
672
*/
673
PHYSFS_DECL const char *PHYSFS_getLastError(void) PHYSFS_DEPRECATED;
674
675
676
/**
677
678
* \fn const char *PHYSFS_getDirSeparator(void)
* \brief Get platform-dependent dir separator string.
679
*
680
* This returns "\\" on win32, "/" on Unix, and ":" on MacOS. It may be more
681
682
683
684
685
686
687
* 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.
688
*/
689
PHYSFS_DECL const char *PHYSFS_getDirSeparator(void);
690
691
693
694
695
696
697
698
* \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.
699
700
701
702
703
704
705
706
707
708
709
710
*
* 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.
*
711
712
713
714
* 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.
*
715
716
717
718
719
* Please note that PHYSFS_stat() will always check the path specified; if
* that path is a symlink, it will not be followed in any case. If symlinks
* aren't permitted through this function, PHYSFS_stat() ignores them, and
* would treat the query as if the path didn't exist at all.
*
720
721
* Symbolic link permission can be enabled or disabled at any time after
* you've called PHYSFS_init(), and is disabled by default.
723
* \param allow nonzero to permit symlinks, zero to deny linking.
724
725
*
* \sa PHYSFS_symbolicLinksPermitted
727
PHYSFS_DECL void PHYSFS_permitSymbolicLinks(int allow);
730
/**
731
732
* \fn char **PHYSFS_getCdRomDirs(void)
* \brief Get an array of paths to available CD-ROM drives.
733
*
734
735
* 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
736
737
738
739
* 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
740
741
742
743
744
745
* call to this function will reflect that change.
*
* This function refers to "CD-ROM" media, but it really means "inserted disc
* media," such as DVD-ROM, HD-DVD, CDRW, and Blu-Ray discs. It looks for
* filesystems, and as such won't report an audio CD, unless there's a
* mounted filesystem track on it.
746
747
748
749
*
* The returned value is an array of strings, with a NULL entry to signify the
* end of the list:
*
751
* char **cds = PHYSFS_getCdRomDirs();
752
753
* char **i;
*
754
* for (i = cds; *i != NULL; i++)
755
* printf("cdrom dir [%s] is available.\n", *i);
756
*
757
* PHYSFS_freeList(cds);
758
* \endcode
760
761
* This call may block while drives spin up. Be forewarned.
*
762
763
764
* When you are done with the returned information, you may dispose of the
* resources by calling PHYSFS_freeList() with the returned pointer.
*
765
* \return Null-terminated array of null-terminated strings.
766
767
*
* \sa PHYSFS_getCdRomDirsCallback
768
*/
769
PHYSFS_DECL char **PHYSFS_getCdRomDirs(void);
770
771
772
/**
773
774
775
* \fn const char *PHYSFS_getBaseDir(void)
* \brief Get the path where the application resides.
*
776
777
* Helper function.
*
778
* Get the "base dir". This is the directory where the application was run
779
780
* from, which is probably the installation directory, and may or may not
* be the process's current working directory.
781
*
782
* You should probably use the base dir in your search path.
783
*
784
785
786
787
788
789
790
791
792
* \warning On most platforms, this is a directory; on Android, this gives
* you the path to the app's package (APK) file. As APK files are
* just .zip files, you can mount them in PhysicsFS like regular
* directories. You'll probably want to call
* PHYSFS_setRoot(basedir, "/assets") after mounting to make your
* app's actual data available directly without all the Android
* metadata and directory offset. Note that if you passed a NULL to
* PHYSFS_init(), you will not get the APK file here.
*
793
794
* \return READ ONLY string of base dir in platform-dependent notation.
*
795
* \sa PHYSFS_getPrefDir
796
*/
797
PHYSFS_DECL const char *PHYSFS_getBaseDir(void);
798
799
800
/**
801
802
803
* \fn const char *PHYSFS_getUserDir(void)
* \brief Get the path where user's home directory resides.
*
804
805
* \deprecated As of PhysicsFS 2.1, you probably want PHYSFS_getPrefDir().
*
806
807
* Helper function.
*
808
* Get the "user dir". This is meant to be a suggestion of where a specific
809
* user of the system can store files. On Unix, this is her home directory.
810
* On systems with no concept of multiple home directories (MacOS, win95),
811
* this will default to something like "C:\mybasedir\users\username"
812
813
* where "username" will either be the login name, or "default" if the
* platform doesn't support multiple users, either.
814
*
815
816
817
* \return READ ONLY string of user dir in platform-dependent notation.
*
* \sa PHYSFS_getBaseDir
818
* \sa PHYSFS_getPrefDir
819
*/
820
PHYSFS_DECL const char *PHYSFS_getUserDir(void) PHYSFS_DEPRECATED;
821
822
823
/**
824
825
826
* \fn const char *PHYSFS_getWriteDir(void)
* \brief Get path where PhysicsFS will allow file writing.
*
827
* Get the current write dir. The default write dir is NULL.
828
*
829
* \return READ ONLY string of write dir in platform-dependent notation,
830
* OR NULL IF NO WRITE PATH IS CURRENTLY SET.
831
832
*
* \sa PHYSFS_setWriteDir
833
*/
834
PHYSFS_DECL const char *PHYSFS_getWriteDir(void);
835
836
837
/**
838
839
840
* \fn int PHYSFS_setWriteDir(const char *newDir)
* \brief Tell PhysicsFS where it may write files.
*
841
* Set a new write dir. This will override the previous setting.
842
*
843
844
* This call will fail (and fail to change the write dir) if the current
* write dir still has files open in it.
845
*
846
* \param newDir The new directory to be the root of the write dir,
847
* specified in platform-dependent notation. Setting to NULL
848
* disables the write dir, so no files can be opened for
849
* writing via PhysicsFS.
850
* \return non-zero on success, zero on failure. All attempts to open a file
851
* for writing via PhysicsFS will fail until this call succeeds.
852
* Use PHYSFS_getLastErrorCode() to obtain the specific error.
853
*
854
* \sa PHYSFS_getWriteDir
855
*/
856
PHYSFS_DECL int PHYSFS_setWriteDir(const char *newDir);
857
858
859
860
861
862
/**
* \fn int PHYSFS_addToSearchPath(const char *newDir, int appendToPath)
* \brief Add an archive or directory to the search path.
*
863
864
865
866
867
868
869
870
* \deprecated As of PhysicsFS 2.0, use PHYSFS_mount() instead. This
* function just wraps it anyhow.
*
* This function is equivalent to:
*
* \code
* PHYSFS_mount(newDir, NULL, appendToPath);
* \endcode
872
873
874
* You must use this and not PHYSFS_mount if binary compatibility with
* PhysicsFS 1.0 is important (which it may not be for many people).
*
875
* \sa PHYSFS_mount
876
877
* \sa PHYSFS_removeFromSearchPath
* \sa PHYSFS_getSearchPath
878
*/
879
880
PHYSFS_DECL int PHYSFS_addToSearchPath(const char *newDir, int appendToPath)
PHYSFS_DEPRECATED;
881
882
/**
883
884
* \fn int PHYSFS_removeFromSearchPath(const char *oldDir)
* \brief Remove a directory or archive from the search path.
885
*
886
887
888
889
890
891
* \deprecated As of PhysicsFS 2.1, use PHYSFS_unmount() instead. This
* function just wraps it anyhow. There's no functional difference
* except the vocabulary changed from "adding to the search path"
* to "mounting" when that functionality was extended, and thus
* the preferred way to accomplish this function's work is now
* called "unmounting."
892
*
893
* This function is equivalent to:
894
*
895
896
897
898
899
900
* \code
* PHYSFS_unmount(oldDir);
* \endcode
*
* You must use this and not PHYSFS_unmount if binary compatibility with
* PhysicsFS 1.0 is important (which it may not be for many people).
901
902
903
*
* \sa PHYSFS_addToSearchPath
* \sa PHYSFS_getSearchPath
904
* \sa PHYSFS_unmount
905
*/
906
907
PHYSFS_DECL int PHYSFS_removeFromSearchPath(const char *oldDir)
PHYSFS_DEPRECATED;
908
909
910
/**
911
912
913
914
* \fn char **PHYSFS_getSearchPath(void)
* \brief Get the current search path.
*
* The default search path is an empty list.
915
916
917
918
*
* The returned value is an array of strings, with a NULL entry to signify the
* end of the list:
*
920
921
922
923
* char **i;
*
* for (i = PHYSFS_getSearchPath(); *i != NULL; i++)
* printf("[%s] is in the search path.\n", *i);
924
* \endcode
925
*
926
927
* When you are done with the returned information, you may dispose of the
* resources by calling PHYSFS_freeList() with the returned pointer.
928
*
929
* \return Null-terminated array of null-terminated strings. NULL if there
930
* was a problem (read: OUT OF MEMORY).
932
* \sa PHYSFS_getSearchPathCallback
933
934
* \sa PHYSFS_addToSearchPath
* \sa PHYSFS_removeFromSearchPath
935
*/
936
PHYSFS_DECL char **PHYSFS_getSearchPath(void);
937
938
939
/**
940
941
942
* \fn int PHYSFS_setSaneConfig(const char *organization, const char *appName, const char *archiveExt, int includeCdRoms, int archivesFirst)
* \brief Set up sane, default paths.
*
943
944
* Helper function.
*
945
946
* The write dir will be set to the pref dir returned by
* \code PHYSFS_getPrefDir(organization, appName) \endcode, which is
947
* created if it doesn't exist.
948
949
*
* The above is sufficient to make sure your program's configuration directory
950
* is separated from other clutter, and platform-independent.
951
952
953
*
* The search path will be:
*
954
955
956
* - The Write Dir (created if it doesn't exist)
* - The Base Dir (PHYSFS_getBaseDir())
* - All found CD-ROM dirs (optionally)
957
958
959
960
961
962
*
* 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
963
964
* order, regardless of which directories they were found in. All archives
* are mounted in the root of the virtual file system ("/").
965
966
*
* All of this can be accomplished from the application, but this just does it
967
* all for you. Feel free to add more to the search path manually, too.
968
*
969
* \param organization Name of your company/group/etc to be used as a
970
971
* dirname, so keep it small, and no-frills.
*
972
* \param appName Program-specific name of your program, to separate it
973
974
* from other programs using PhysicsFS.
*
975
* \param archiveExt File extension used by your program to specify an
976
977
* archive. For example, Quake 3 uses "pk3", even though
* they are just zipfiles. Specify NULL to not dig out
978
979
980
* 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.
981
*
982
* \param includeCdRoms Non-zero to include CD-ROMs in the search path, and
983
984
985
986
987
988
989
* (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.
990
*
991
* \param archivesFirst Non-zero to prepend the archives to the search path.
992
* Zero to append them. Ignored if !(archiveExt).
994
995
* \return nonzero on success, zero on error. Use PHYSFS_getLastErrorCode()
* to obtain the specific error.
996
*/
997
998
999
1000
PHYSFS_DECL int PHYSFS_setSaneConfig(const char *organization,
const char *appName,
const char *archiveExt,
int includeCdRoms,