Skip to content

Latest commit

 

History

History
2476 lines (2250 loc) · 94.1 KB

physfs.h

File metadata and controls

2476 lines (2250 loc) · 94.1 KB
 
Jun 7, 2002
Jun 7, 2002
1
2
/** \file physfs.h */
Jun 7, 2001
Jun 7, 2001
3
/**
Jun 7, 2002
Jun 7, 2002
4
5
6
7
8
* \mainpage PhysicsFS
*
* The latest version of PhysicsFS can be found at:
* http://icculus.org/physfs/
*
Jun 7, 2001
Jun 7, 2001
9
10
11
12
13
14
15
16
17
18
19
* PhysicsFS; a portable, flexible file i/o abstraction.
*
* This API gives you access to a system file system in ways superior to the
* stdio or system i/o calls. The brief benefits:
*
* - It's portable.
* - It's safe. No file access is permitted outside the specified dirs.
* - It's flexible. Archives (.ZIP files) can be used transparently as
* directory structures.
*
* This system is largely inspired by Quake 3's PK3 files and the related
Jun 7, 2001
Jun 7, 2001
20
* fs_* cvars. If you've ever tinkered with these, then this API will be
Jun 7, 2001
Jun 7, 2001
21
22
* familiar to you.
*
Jul 5, 2001
Jul 5, 2001
23
24
25
26
27
28
* With PhysicsFS, you have a single writing directory and multiple
* directories (the "search path") for reading. You can think of this as a
* filesystem within a filesystem. If (on Windows) you were to set the
* writing directory to "C:\MyGame\MyWritingDirectory", then no PHYSFS calls
* could touch anything above this directory, including the "C:\MyGame" and
* "C:\" directories. This prevents an application's internal scripting
Jan 8, 2004
Jan 8, 2004
29
* language from piddling over c:\\config.sys, for example. If you'd rather
Jul 5, 2001
Jul 5, 2001
30
31
* give PHYSFS full access to the system's REAL file system, set the writing
* dir to "C:\", but that's generally A Bad Thing for several reasons.
Jun 7, 2001
Jun 7, 2001
32
33
*
* Drive letters are hidden in PhysicsFS once you set up your initial paths.
Jul 5, 2001
Jul 5, 2001
34
* The search path creates a single, hierarchical directory structure.
Jun 7, 2001
Jun 7, 2001
35
36
37
38
39
40
41
* Not only does this lend itself well to general abstraction with archives,
* it also gives better support to operating systems like MacOS and Unix.
* Generally speaking, you shouldn't ever hardcode a drive letter; not only
* does this hurt portability to non-Microsoft OSes, but it limits your win32
* users to a single drive, too. Use the PhysicsFS abstraction functions and
* allow user-defined configuration options, too. When opening a file, you
* specify it like it was on a Unix filesystem: if you want to write to
Jul 5, 2001
Jul 5, 2001
42
* "C:\MyGame\MyConfigFiles\game.cfg", then you might set the write dir to
Jun 7, 2001
Jun 7, 2001
43
* "C:\MyGame" and then open "MyConfigFiles/game.cfg". This gives an
Jun 7, 2001
Jun 7, 2001
44
* abstraction across all platforms. Specifying a file in this way is termed
Jul 5, 2001
Jul 5, 2001
45
46
47
48
49
50
51
52
* "platform-independent notation" in this documentation. Specifying a
* a filename in a form such as "C:\mydir\myfile" or
* "MacOS hard drive:My Directory:My File" is termed "platform-dependent
* notation". The only time you use platform-dependent notation is when
* setting up your write directory and search path; after that, all file
* access into those directories are done with platform-independent notation.
*
* All files opened for writing are opened in relation to the write directory,
Jun 7, 2001
Jun 7, 2001
53
* which is the root of the writable filesystem. When opening a file for
Jul 5, 2001
Jul 5, 2001
54
* reading, PhysicsFS goes through the search path. This is NOT the
Jun 7, 2001
Jun 7, 2001
55
56
57
58
59
60
* same thing as the PATH environment variable. An application using
* PhysicsFS specifies directories to be searched which may be actual
* directories, or archive files that contain files and subdirectories of
* their own. See the end of these docs for currently supported archive
* formats.
*
Jul 5, 2001
Jul 5, 2001
61
* Once the search path is defined, you may open files for reading. If you've
Jun 7, 2001
Jun 7, 2001
62
63
* got the following search path defined (to use a win32 example again):
*
Jan 8, 2004
Jan 8, 2004
64
65
66
67
* - C:\\mygame
* - C:\\mygame\\myuserfiles
* - D:\\mygamescdromdatafiles
* - C:\\mygame\\installeddatafiles.zip
Jun 7, 2001
Jun 7, 2001
68
*
Jul 5, 2001
Jul 5, 2001
69
* Then a call to PHYSFS_openRead("textfiles/myfile.txt") (note the directory
Jun 7, 2001
Jun 7, 2001
70
71
* separator, lack of drive letter, and lack of dir separator at the start of
* the string; this is platform-independent notation) will check for
Jan 8, 2004
Jan 8, 2004
72
73
74
75
76
77
78
* C:\\mygame\\textfiles\\myfile.txt, then
* C:\\mygame\\myuserfiles\\textfiles\\myfile.txt, then
* D:\\mygamescdromdatafiles\\textfiles\\myfile.txt, then, finally, for
* textfiles\\myfile.txt inside of C:\\mygame\\installeddatafiles.zip.
* Remember that most archive types and platform filesystems store their
* filenames in a case-sensitive manner, so you should be careful to specify
* it correctly.
Jun 7, 2001
Jun 7, 2001
79
*
Jul 5, 2001
Jul 5, 2001
80
* Files opened through PhysicsFS may NOT contain "." or ".." or ":" as dir
Mar 13, 2005
Mar 13, 2005
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.
Jul 5, 2001
Jul 5, 2001
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.
Jun 7, 2001
Jun 7, 2001
94
95
96
*
* All files are opened in binary mode; there is no endline conversion for
* textfiles. Other than that, PhysicsFS has some convenience functions for
Jun 28, 2001
Jun 28, 2001
97
* platform-independence. There is a function to tell you the current
Jul 5, 2001
Jul 5, 2001
98
* platform's dir separator ("\\" on windows, "/" on Unix, ":" on MacOS),
Jun 28, 2001
Jun 28, 2001
99
100
101
* which is needed only to set up your search/write paths. There is a
* function to tell you what CD-ROM drives contain accessible discs, and a
* function to recommend a good search path, etc.
Jun 7, 2001
Jun 7, 2001
102
*
Jul 5, 2001
Jul 5, 2001
103
104
* A recommended order for the search path is the write dir, then the base dir,
* then the cdrom dir, then any archives discovered. Quake 3 does something
Jun 28, 2001
Jun 28, 2001
105
106
* like this, but moves the archives to the start of the search path. Build
* Engine games, like Duke Nukem 3D and Blood, place the archives last, and
Jul 5, 2001
Jul 5, 2001
107
108
* use the base dir for both searching and writing. There is a helper
* function (PHYSFS_setSaneConfig()) that puts together a basic configuration
Jun 28, 2001
Jun 28, 2001
109
* for you, based on a few parameters. Also see the comments on
Jul 5, 2001
Jul 5, 2001
110
111
112
* PHYSFS_getBaseDir(), and PHYSFS_getUserDir() for info on what those
* are and how they can help you determine an optimal search path.
*
Mar 13, 2005
Mar 13, 2005
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.
*
Mar 30, 2002
Mar 30, 2002
125
126
127
128
129
130
* 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
131
132
133
*
* 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
134
* filehandles with PhysicsFS and vice versa.
Jun 7, 2001
Jun 7, 2001
135
136
*
* Note that archives need not be named as such: if you have a ZIP file and
Jun 28, 2001
Jun 28, 2001
137
* rename it with a .PKG extension, the file will still be recognized as a
Jun 7, 2001
Jun 7, 2001
138
* ZIP archive by PhysicsFS; the file's contents are used to determine its
Mar 13, 2005
Mar 13, 2005
139
* type where possible.
Jun 7, 2001
Jun 7, 2001
140
141
142
*
* Currently supported archive types:
* - .ZIP (pkZip/WinZip/Info-ZIP compatible)
Jun 7, 2002
Jun 7, 2002
143
* - .GRP (Build Engine groupfile archives)
Mar 30, 2003
Mar 30, 2003
144
* - .PAK (Quake I/II archive format)
Mar 30, 2003
Mar 30, 2003
145
146
* - .HOG (Descent I/II HOG file archives)
* - .MVL (Descent II movielib archives)
Dec 15, 2003
Dec 15, 2003
147
* - .WAD (DOOM engine archives)
Jun 7, 2002
Jun 7, 2002
148
*
Nov 5, 2006
Nov 5, 2006
149
150
151
*
* String policy for PhysicsFS 2.0 and later:
*
Mar 11, 2007
Mar 11, 2007
152
153
154
155
156
* 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.
Nov 5, 2006
Nov 5, 2006
157
158
159
160
161
162
163
164
*
* 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
* offers. If you are on Windows and build with Unicode support, your TCHAR
* strings are two bytes per character (this is called "UCS-2 encoding"). You
* should convert them to UTF-8 before handing them to PhysicsFS with
Mar 16, 2007
Mar 16, 2007
165
* PHYSFS_utf8FromUcs2(). If you're using Unix or Mac OS X, your wchar_t
Nov 5, 2006
Nov 5, 2006
166
* strings are four bytes per character ("UCS-4 encoding"). Use
Mar 16, 2007
Mar 16, 2007
167
* PHYSFS_utf8FromUcs4(). Mac OS X can give you UTF-8 directly from a
Mar 8, 2007
Mar 8, 2007
168
169
170
171
172
173
174
* CFString, 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!
Nov 5, 2006
Nov 5, 2006
175
*
Mar 16, 2007
Mar 16, 2007
176
* Naturally, there's also PHYSFS_utf8ToUcs2() and PHYSFS_utf8ToUcs4() to get
Nov 5, 2006
Nov 5, 2006
177
178
179
180
181
182
183
* 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.
*
* PhysicsFS offers basic encoding conversion support, but not a whole string
* library. Get your stuff into whatever format you can work with.
*
Mar 11, 2007
Mar 11, 2007
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
* Some platforms and archivers don't offer full Unicode support behind the
* scenes. For example, OS/2 only offers "codepages" and the filesystem
* itself doesn't support multibyte encodings. We make an earnest effort to
* convert to/from the current locale here, but all bets are off if
* you want to hand an arbitrary Japanese character through to these systems.
* Modern OSes (Mac OS X, Linux, Windows, PocketPC, etc) should all be fine.
* Many game-specific archivers are seriously unprepared for Unicode (the
* 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.
*
Nov 5, 2006
Nov 5, 2006
200
201
202
*
* Other stuff:
*
Mar 11, 2007
Mar 11, 2007
203
* Please see the file LICENSE.txt in the source's root directory for licensing
Jun 7, 2002
Jun 7, 2002
204
* and redistribution rights.
Jun 7, 2001
Jun 7, 2001
205
*
Mar 11, 2007
Mar 11, 2007
206
* Please see the file CREDITS.txt in the source's root directory for a more or
Mar 13, 2005
Mar 13, 2005
207
* less complete list of who's responsible for this.
Jun 7, 2001
Jun 7, 2001
208
*
Jun 7, 2002
Jun 7, 2002
209
* \author Ryan C. Gordon.
Jun 7, 2001
Jun 7, 2001
210
211
212
213
214
215
216
217
218
*/
#ifndef _INCLUDE_PHYSFS_H_
#define _INCLUDE_PHYSFS_H_
#ifdef __cplusplus
extern "C" {
#endif
Jan 29, 2010
Jan 29, 2010
219
220
#if defined(PHYSFS_DECL)
/* do nothing. */
Jan 29, 2010
Jan 29, 2010
221
222
#elif (defined SWIG)
#define PHYSFS_DECL extern
Jan 29, 2010
Jan 29, 2010
223
224
#elif (defined _MSC_VER)
#define PHYSFS_DECL __declspec(dllexport)
Apr 17, 2009
Apr 17, 2009
225
#elif (defined __SUNPRO_C)
Jan 29, 2010
Jan 29, 2010
226
#define PHYSFS_DECL __global
Apr 21, 2009
Apr 21, 2009
227
#elif ((__GNUC__ >= 3) && (!__EMX__) && (!sun))
Jan 29, 2010
Jan 29, 2010
228
#define PHYSFS_DECL __attribute__((visibility("default")))
Aug 23, 2001
Aug 23, 2001
229
#else
Jan 29, 2010
Jan 29, 2010
230
#define PHYSFS_DECL
Aug 23, 2001
Aug 23, 2001
231
232
#endif
Jan 29, 2010
Jan 29, 2010
233
234
235
236
237
238
239
240
241
242
243
244
#if 0 /* !!! FIXME: look into this later. */
#if defined(PHYSFS_CALL)
/* do nothing. */
#elif defined(__WIN32__) && !defined(__GNUC__)
#define PHYSFS_CALL __cdecl
#elif defined(__OS2__) /* use _System, so it works across all compilers. */
#define PHYSFS_CALL _System
#else
#define PHYSFS_CALL
#endif
#endif
Jun 7, 2002
Jun 7, 2002
245
246
247
248
/**
* \typedef PHYSFS_uint8
* \brief An unsigned, 8-bit integer type.
*/
Mar 24, 2002
Mar 24, 2002
249
typedef unsigned char PHYSFS_uint8;
Jun 7, 2002
Jun 7, 2002
250
251
252
253
254
/**
* \typedef PHYSFS_sint8
* \brief A signed, 8-bit integer type.
*/
Mar 24, 2002
Mar 24, 2002
255
typedef signed char PHYSFS_sint8;
Jun 7, 2002
Jun 7, 2002
256
257
258
259
260
/**
* \typedef PHYSFS_uint16
* \brief An unsigned, 16-bit integer type.
*/
Mar 24, 2002
Mar 24, 2002
261
typedef unsigned short PHYSFS_uint16;
Jun 7, 2002
Jun 7, 2002
262
263
264
265
266
/**
* \typedef PHYSFS_sint16
* \brief A signed, 16-bit integer type.
*/
Mar 24, 2002
Mar 24, 2002
267
typedef signed short PHYSFS_sint16;
Jun 7, 2002
Jun 7, 2002
268
269
270
271
272
/**
* \typedef PHYSFS_uint32
* \brief An unsigned, 32-bit integer type.
*/
Mar 24, 2002
Mar 24, 2002
273
typedef unsigned int PHYSFS_uint32;
Jun 7, 2002
Jun 7, 2002
274
275
276
277
278
/**
* \typedef PHYSFS_sint32
* \brief A signed, 32-bit integer type.
*/
Mar 24, 2002
Mar 24, 2002
279
280
typedef signed int PHYSFS_sint32;
Jun 7, 2002
Jun 7, 2002
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
/**
* \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
296
#if (defined PHYSFS_NO_64BIT_SUPPORT) /* oh well. */
Mar 24, 2002
Mar 24, 2002
297
298
typedef PHYSFS_uint32 PHYSFS_uint64;
typedef PHYSFS_sint32 PHYSFS_sint64;
Apr 12, 2002
Apr 12, 2002
299
300
301
#elif (defined _MSC_VER)
typedef signed __int64 PHYSFS_sint64;
typedef unsigned __int64 PHYSFS_uint64;
Mar 24, 2002
Mar 24, 2002
302
303
304
305
306
#else
typedef unsigned long long PHYSFS_uint64;
typedef signed long long PHYSFS_sint64;
#endif
Jun 7, 2002
Jun 7, 2002
307
Jan 29, 2010
Jan 29, 2010
308
#ifndef SWIG
Jun 7, 2002
Jun 7, 2002
309
#ifndef DOXYGEN_SHOULD_IGNORE_THIS
Mar 24, 2002
Mar 24, 2002
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
/* 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
328
#endif /* DOXYGEN_SHOULD_IGNORE_THIS */
Jan 29, 2010
Jan 29, 2010
329
#endif /* SWIG */
Mar 24, 2002
Mar 24, 2002
330
331
Jun 7, 2002
Jun 7, 2002
332
/**
Sep 26, 2004
Sep 26, 2004
333
* \struct PHYSFS_File
Jun 7, 2002
Jun 7, 2002
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
* \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
352
353
* \sa PHYSFS_setBuffer
* \sa PHYSFS_flush
Jun 7, 2002
Jun 7, 2002
354
*/
Nov 2, 2008
Nov 2, 2008
355
typedef struct PHYSFS_File
Jun 28, 2001
Jun 28, 2001
356
{
Jun 7, 2002
Jun 7, 2002
357
void *opaque; /**< That's all you get. Don't touch. */
Sep 26, 2004
Sep 26, 2004
358
} PHYSFS_File;
Jun 28, 2001
Jun 28, 2001
359
Mar 16, 2007
Mar 16, 2007
360
361
362
363
364
365
366
367
368
369
370
371
372
/**
* \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
Jun 28, 2001
Jun 28, 2001
373
374
Jun 7, 2002
Jun 7, 2002
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
/**
* \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
*/
Nov 2, 2008
Nov 2, 2008
390
typedef struct PHYSFS_ArchiveInfo
Jun 7, 2002
Jun 7, 2002
391
392
393
394
395
396
{
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
397
Dec 1, 2002
Dec 1, 2002
398
Jun 7, 2002
Jun 7, 2002
399
400
401
402
403
404
405
406
407
408
409
/**
* \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
Sep 23, 2006
Sep 23, 2006
410
* \sa PHYSFS_getLinkedVersion
Jun 7, 2002
Jun 7, 2002
411
*/
Nov 2, 2008
Nov 2, 2008
412
typedef struct PHYSFS_Version
Jul 5, 2001
Jul 5, 2001
413
{
Jun 7, 2002
Jun 7, 2002
414
415
416
PHYSFS_uint8 major; /**< major revision */
PHYSFS_uint8 minor; /**< minor revision */
PHYSFS_uint8 patch; /**< patchlevel */
Jul 5, 2001
Jul 5, 2001
417
418
} PHYSFS_Version;
Jan 29, 2010
Jan 29, 2010
419
420
421
422
#ifndef SWIG /* not available from scripting languages. */
Jun 7, 2002
Jun 7, 2002
423
#ifndef DOXYGEN_SHOULD_IGNORE_THIS
Mar 23, 2009
Mar 23, 2009
424
#define PHYSFS_VER_MAJOR 2
Mar 28, 2009
Mar 28, 2009
425
#define PHYSFS_VER_MINOR 1
Mar 23, 2009
Mar 23, 2009
426
#define PHYSFS_VER_PATCH 0
Jun 7, 2002
Jun 7, 2002
427
428
#endif /* DOXYGEN_SHOULD_IGNORE_THIS */
Dec 1, 2002
Dec 1, 2002
429
430
431
/* PhysicsFS state stuff ... */
Jun 7, 2002
Jun 7, 2002
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
/**
* \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
454
Jan 29, 2010
Jan 29, 2010
455
456
#endif /* SWIG */
Jul 5, 2001
Jul 5, 2001
457
458
/**
Jun 7, 2002
Jun 7, 2002
459
460
461
462
463
* \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
464
465
466
467
*
* This is a real function; the macro PHYSFS_VERSION tells you what version
* of PhysFS you compiled against:
*
Jun 7, 2002
Jun 7, 2002
468
* \code
Jul 5, 2001
Jul 5, 2001
469
470
471
472
473
474
475
476
477
* 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
478
* \endcode
Jul 5, 2001
Jul 5, 2001
479
480
*
* This function may be called safely at any time, even before PHYSFS_init().
Jun 7, 2002
Jun 7, 2002
481
482
*
* \sa PHYSFS_VERSION
Jul 5, 2001
Jul 5, 2001
483
*/
Jan 29, 2010
Jan 29, 2010
484
PHYSFS_DECL void PHYSFS_getLinkedVersion(PHYSFS_Version *ver);
Jul 5, 2001
Jul 5, 2001
485
486
Jun 7, 2001
Jun 7, 2001
487
/**
Jun 7, 2002
Jun 7, 2002
488
489
490
491
* \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
492
*
Jul 8, 2001
Jul 8, 2001
493
494
495
* This should be called prior to any attempts to change your process's
* current working directory.
*
Jun 7, 2002
Jun 7, 2002
496
497
498
499
500
501
* \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
502
* gleaned from PHYSFS_getLastError().
Jun 7, 2002
Jun 7, 2002
503
504
*
* \sa PHYSFS_deinit
Apr 1, 2007
Apr 1, 2007
505
* \sa PHYSFS_isInit
Jun 7, 2001
Jun 7, 2001
506
*/
Jan 29, 2010
Jan 29, 2010
507
PHYSFS_DECL int PHYSFS_init(const char *argv0);
Jun 7, 2001
Jun 7, 2001
508
509
510
/**
Jun 7, 2002
Jun 7, 2002
511
512
513
514
515
* \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
516
*
Jul 7, 2001
Jul 7, 2001
517
518
519
520
521
522
* 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
523
*
Jul 7, 2001
Jul 7, 2001
524
* Once successfully deinitialized, PHYSFS_init() can be called again to
May 11, 2007
May 11, 2007
525
526
527
* 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.
Jul 5, 2001
Jul 5, 2001
528
*
Jun 7, 2002
Jun 7, 2002
529
* \return nonzero on success, zero on error. Specifics of the error can be
Jun 7, 2001
Jun 7, 2001
530
531
* gleaned from PHYSFS_getLastError(). If failure, state of PhysFS is
* undefined, and probably badly screwed up.
Jun 7, 2002
Jun 7, 2002
532
533
*
* \sa PHYSFS_init
Apr 1, 2007
Apr 1, 2007
534
* \sa PHYSFS_isInit
Jun 7, 2001
Jun 7, 2001
535
*/
Jan 29, 2010
Jan 29, 2010
536
PHYSFS_DECL int PHYSFS_deinit(void);
Jun 7, 2001
Jun 7, 2001
537
Jun 7, 2001
Jun 7, 2001
538
Jun 28, 2001
Jun 28, 2001
539
/**
Jun 7, 2002
Jun 7, 2002
540
541
542
* \fn const PHYSFS_ArchiveInfo **PHYSFS_supportedArchiveTypes(void)
* \brief Get a list of supported archive types.
*
Jun 28, 2001
Jun 28, 2001
543
544
545
546
547
548
* 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
549
550
* 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
551
*
Jun 7, 2002
Jun 7, 2002
552
* \code
Jun 28, 2001
Jun 28, 2001
553
554
555
556
557
* PHYSFS_ArchiveInfo **i;
*
* for (i = PHYSFS_supportedArchiveTypes(); *i != NULL; i++)
* {
* printf("Supported archive: [%s], which is [%s].\n",
Nov 2, 2008
Nov 2, 2008
558
* (*i)->extension, (*i)->description);
Jun 28, 2001
Jun 28, 2001
559
* }
Jun 7, 2002
Jun 7, 2002
560
* \endcode
Jun 28, 2001
Jun 28, 2001
561
562
563
564
*
* The return values are pointers to static internal memory, and should
* be considered READ ONLY, and never freed.
*
Jun 7, 2002
Jun 7, 2002
565
* \return READ ONLY Null-terminated array of READ ONLY structures.
Jun 28, 2001
Jun 28, 2001
566
*/
Jan 29, 2010
Jan 29, 2010
567
PHYSFS_DECL const PHYSFS_ArchiveInfo **PHYSFS_supportedArchiveTypes(void);
Jun 28, 2001
Jun 28, 2001
568
569
570
/**
Jun 7, 2002
Jun 7, 2002
571
572
573
* \fn void PHYSFS_freeList(void *listVar)
* \brief Deallocate resources of lists returned by PhysicsFS.
*
Jun 28, 2001
Jun 28, 2001
574
575
576
* Certain PhysicsFS functions return lists of information that are
* dynamically allocated. Use this function to free those resources.
*
Mar 28, 2009
Mar 28, 2009
577
578
579
* It is safe to pass a NULL here, but doing so will cause a crash in versions
* before PhysicsFS 2.1.0.
*
Jun 7, 2002
Jun 7, 2002
580
* \param listVar List of information specified as freeable by this function.
Mar 28, 2009
Mar 28, 2009
581
* Passing NULL is safe; it is a valid no-op.
Jun 7, 2002
Jun 7, 2002
582
583
584
585
*
* \sa PHYSFS_getCdRomDirs
* \sa PHYSFS_enumerateFiles
* \sa PHYSFS_getSearchPath
Jun 28, 2001
Jun 28, 2001
586
*/
Jan 29, 2010
Jan 29, 2010
587
PHYSFS_DECL void PHYSFS_freeList(void *listVar);
Jun 28, 2001
Jun 28, 2001
588
589
Jun 7, 2001
Jun 7, 2001
590
/**
Jun 7, 2002
Jun 7, 2002
591
592
593
* \fn const char *PHYSFS_getLastError(void)
* \brief Get human-readable error information.
*
Mar 14, 2005
Mar 14, 2005
594
595
596
597
598
599
600
601
602
603
604
* Get the last PhysicsFS error message as a human-readable, null-terminated
* string. This will be NULL if there's been no error since the last call to
* this 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().
*
* It is not wise to expect a specific string of characters here, since the
* error message may be localized into an unfamiliar language. These strings
* are meant to be passed on directly to the user.
Jun 7, 2001
Jun 7, 2001
605
*
Jun 7, 2002
Jun 7, 2002
606
* \return READ ONLY string of last error message.
Jun 7, 2001
Jun 7, 2001
607
*/
Jan 29, 2010
Jan 29, 2010
608
PHYSFS_DECL const char *PHYSFS_getLastError(void);
Jun 7, 2001
Jun 7, 2001
609
610
611
/**
Jun 7, 2002
Jun 7, 2002
612
613
* \fn const char *PHYSFS_getDirSeparator(void)
* \brief Get platform-dependent dir separator string.
Jun 7, 2001
Jun 7, 2001
614
*
Apr 3, 2007
Apr 3, 2007
615
* This returns "\\" on win32, "/" on Unix, and ":" on MacOS. It may be more
Jun 7, 2002
Jun 7, 2002
616
617
618
619
620
621
622
* 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
623
*/
Jan 29, 2010
Jan 29, 2010
624
PHYSFS_DECL const char *PHYSFS_getDirSeparator(void);
Jun 7, 2001
Jun 7, 2001
625
626
Jul 7, 2001
Jul 7, 2001
627
/**
Jun 7, 2002
Jun 7, 2002
628
629
630
631
632
633
* \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
634
635
636
637
638
639
640
641
642
643
644
645
*
* 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
646
647
648
649
* 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
650
651
* 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
652
*
Jun 7, 2002
Jun 7, 2002
653
* \param allow nonzero to permit symlinks, zero to deny linking.
Apr 1, 2007
Apr 1, 2007
654
655
*
* \sa PHYSFS_symbolicLinksPermitted
Jul 7, 2001
Jul 7, 2001
656
*/
Jan 29, 2010
Jan 29, 2010
657
PHYSFS_DECL void PHYSFS_permitSymbolicLinks(int allow);
Jul 7, 2001
Jul 7, 2001
658
659
Apr 2, 2007
Apr 2, 2007
660
/* !!! FIXME: const this? */
Jun 7, 2001
Jun 7, 2001
661
/**
Jun 7, 2002
Jun 7, 2002
662
663
* \fn char **PHYSFS_getCdRomDirs(void)
* \brief Get an array of paths to available CD-ROM drives.
Jun 7, 2001
Jun 7, 2001
664
*
Jul 5, 2001
Jul 5, 2001
665
666
* 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
667
668
669
670
* 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
Apr 2, 2007
Apr 2, 2007
671
672
673
674
675
676
* 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.
Jun 7, 2001
Jun 7, 2001
677
678
679
680
*
* 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
681
* \code
Jul 6, 2001
Jul 6, 2001
682
* char **cds = PHYSFS_getCdRomDirs();
Jun 7, 2001
Jun 7, 2001
683
684
* char **i;
*
Jul 6, 2001
Jul 6, 2001
685
* for (i = cds; *i != NULL; i++)
Jul 5, 2001
Jul 5, 2001
686
* printf("cdrom dir [%s] is available.\n", *i);
Jun 7, 2001
Jun 7, 2001
687
*
Jul 6, 2001
Jul 6, 2001
688
* PHYSFS_freeList(cds);
Jun 7, 2002
Jun 7, 2002
689
* \endcode
Jul 6, 2001
Jul 6, 2001
690
*
Jun 7, 2001
Jun 7, 2001
691
692
* This call may block while drives spin up. Be forewarned.
*
Jun 28, 2001
Jun 28, 2001
693
694
695
* 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
696
* \return Null-terminated array of null-terminated strings.
Mar 14, 2005
Mar 14, 2005
697
698
*
* \sa PHYSFS_getCdRomDirsCallback
Jun 7, 2001
Jun 7, 2001
699
*/
Jan 29, 2010
Jan 29, 2010
700
PHYSFS_DECL char **PHYSFS_getCdRomDirs(void);
Jun 7, 2001
Jun 7, 2001
701
702
703
/**
Jun 7, 2002
Jun 7, 2002
704
705
706
* \fn const char *PHYSFS_getBaseDir(void)
* \brief Get the path where the application resides.
*
Jun 7, 2001
Jun 7, 2001
707
708
* Helper function.
*
Jul 5, 2001
Jul 5, 2001
709
* Get the "base dir". This is the directory where the application was run
Jun 28, 2001
Jun 28, 2001
710
711
* 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
712
*
Jul 5, 2001
Jul 5, 2001
713
* You should probably use the base dir in your search path.
Jun 7, 2001
Jun 7, 2001
714
*
Jun 7, 2002
Jun 7, 2002
715
716
717
* \return READ ONLY string of base dir in platform-dependent notation.
*
* \sa PHYSFS_getUserDir
Jun 7, 2001
Jun 7, 2001
718
*/
Jan 29, 2010
Jan 29, 2010
719
PHYSFS_DECL const char *PHYSFS_getBaseDir(void);
Jun 7, 2001
Jun 7, 2001
720
721
722
/**
Jun 7, 2002
Jun 7, 2002
723
724
725
* \fn const char *PHYSFS_getUserDir(void)
* \brief Get the path where user's home directory resides.
*
Jun 7, 2001
Jun 7, 2001
726
727
* Helper function.
*
Jul 5, 2001
Jul 5, 2001
728
* Get the "user dir". This is meant to be a suggestion of where a specific
Jun 7, 2001
Jun 7, 2001
729
* user of the system can store files. On Unix, this is her home directory.
Jun 28, 2001
Jun 28, 2001
730
* On systems with no concept of multiple home directories (MacOS, win95),
Jul 5, 2001
Jul 5, 2001
731
* this will default to something like "C:\mybasedir\users\username"
Jun 28, 2001
Jun 28, 2001
732
733
* 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
734
*
Jul 5, 2001
Jul 5, 2001
735
* You should probably use the user dir as the basis for your write dir, and
Jun 7, 2001
Jun 7, 2001
736
737
* also put it near the beginning of your search path.
*
Jun 7, 2002
Jun 7, 2002
738
739
740
* \return READ ONLY string of user dir in platform-dependent notation.
*
* \sa PHYSFS_getBaseDir
Jun 7, 2001
Jun 7, 2001
741
*/
Jan 29, 2010
Jan 29, 2010
742
PHYSFS_DECL const char *PHYSFS_getUserDir(void);
Jun 7, 2001
Jun 7, 2001
743
744
745
/**
Jun 7, 2002
Jun 7, 2002
746
747
748
* \fn const char *PHYSFS_getWriteDir(void)
* \brief Get path where PhysicsFS will allow file writing.
*
Jul 5, 2001
Jul 5, 2001
749
* Get the current write dir. The default write dir is NULL.
Jun 7, 2001
Jun 7, 2001
750
*
Jun 7, 2002
Jun 7, 2002
751
* \return READ ONLY string of write dir in platform-dependent notation,
Jun 7, 2001
Jun 7, 2001
752
* OR NULL IF NO WRITE PATH IS CURRENTLY SET.
Jun 7, 2002
Jun 7, 2002
753
754
*
* \sa PHYSFS_setWriteDir
Jun 7, 2001
Jun 7, 2001
755
*/
Jan 29, 2010
Jan 29, 2010
756
PHYSFS_DECL const char *PHYSFS_getWriteDir(void);
Jun 7, 2001
Jun 7, 2001
757
758
759
/**
Jun 7, 2002
Jun 7, 2002
760
761
762
* \fn int PHYSFS_setWriteDir(const char *newDir)
* \brief Tell PhysicsFS where it may write files.
*
Nov 28, 2005
Nov 28, 2005
763
* Set a new write dir. This will override the previous setting.
Jun 7, 2001
Jun 7, 2001
764
*
Jul 5, 2001
Jul 5, 2001
765
766
* 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
767
*
Jun 7, 2002
Jun 7, 2002
768
* \param newDir The new directory to be the root of the write dir,
Jun 28, 2001
Jun 28, 2001
769
* specified in platform-dependent notation. Setting to NULL
Jul 5, 2001
Jul 5, 2001
770
* disables the write dir, so no files can be opened for
Jun 7, 2001
Jun 7, 2001
771
* writing via PhysicsFS.
Jun 7, 2002
Jun 7, 2002
772
* \return non-zero on success, zero on failure. All attempts to open a file
Jun 7, 2001
Jun 7, 2001
773
774
775
* 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
776
* \sa PHYSFS_getWriteDir
Jun 7, 2001
Jun 7, 2001
777
*/
Jan 29, 2010
Jan 29, 2010
778
PHYSFS_DECL int PHYSFS_setWriteDir(const char *newDir);
Jun 7, 2001
Jun 7, 2001
779
780
Mar 13, 2005
Mar 13, 2005
781
782
783
784
/**
* \fn int PHYSFS_addToSearchPath(const char *newDir, int appendToPath)
* \brief Add an archive or directory to the search path.
*
Mar 14, 2005
Mar 14, 2005
785
* This is a legacy call in PhysicsFS 2.0, equivalent to:
Mar 13, 2005
Mar 13, 2005
786
* PHYSFS_mount(newDir, NULL, appendToPath);
Jun 7, 2002
Jun 7, 2002
787
*
Mar 14, 2005
Mar 14, 2005
788
789
790
* 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).
*
Mar 13, 2005
Mar 13, 2005
791
* \sa PHYSFS_mount
Jun 7, 2002
Jun 7, 2002
792
793
* \sa PHYSFS_removeFromSearchPath
* \sa PHYSFS_getSearchPath
Jun 7, 2001
Jun 7, 2001
794
*/
Jan 29, 2010
Jan 29, 2010
795
PHYSFS_DECL int PHYSFS_addToSearchPath(const char *newDir, int appendToPath);
Jun 7, 2001
Jun 7, 2001
796
797
798
/**
Jun 7, 2002
Jun 7, 2002
799
800
* \fn int PHYSFS_removeFromSearchPath(const char *oldDir)
* \brief Remove a directory or archive from the search path.
Jun 7, 2001
Jun 7, 2001
801
802
803
804
805
806
807
*
* 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
808
809
* \param oldDir dir/archive to remove.
* \return nonzero on success, zero on failure.
Jun 7, 2001
Jun 7, 2001
810
* Specifics of the error can be gleaned from PHYSFS_getLastError().
Jun 7, 2002
Jun 7, 2002
811
812
813
*
* \sa PHYSFS_addToSearchPath
* \sa PHYSFS_getSearchPath
Jun 7, 2001
Jun 7, 2001
814
*/
Jan 29, 2010
Jan 29, 2010
815
PHYSFS_DECL int PHYSFS_removeFromSearchPath(const char *oldDir);
Jun 7, 2001
Jun 7, 2001
816
817
818
/**
Jun 7, 2002
Jun 7, 2002
819
820
821
822
* \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
823
824
825
826
*
* 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
827
* \code
Jun 7, 2001
Jun 7, 2001
828
829
830
831
* char **i;
*
* for (i = PHYSFS_getSearchPath(); *i != NULL; i++)
* printf("[%s] is in the search path.\n", *i);
Jun 7, 2002
Jun 7, 2002
832
* \endcode
Jun 7, 2001
Jun 7, 2001
833
*
Jun 28, 2001
Jun 28, 2001
834
835
* 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
836
*
Jun 7, 2002
Jun 7, 2002
837
* \return Null-terminated array of null-terminated strings. NULL if there
Jul 5, 2001
Jul 5, 2001
838
* was a problem (read: OUT OF MEMORY).
Jun 7, 2002
Jun 7, 2002
839
*
Mar 14, 2005
Mar 14, 2005
840
* \sa PHYSFS_getSearchPathCallback
Jun 7, 2002
Jun 7, 2002
841
842
* \sa PHYSFS_addToSearchPath
* \sa PHYSFS_removeFromSearchPath
Jun 7, 2001
Jun 7, 2001
843
*/
Jan 29, 2010
Jan 29, 2010
844
PHYSFS_DECL char **PHYSFS_getSearchPath(void);
Jun 7, 2001
Jun 7, 2001
845
846
847
/**
Jun 7, 2002
Jun 7, 2002
848
849
850
* \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
851
852
* Helper function.
*
Jun 7, 2002
Jun 7, 2002
853
854
* The write dir will be set to "userdir/.organization/appName", which is
* created if it doesn't exist.
Jun 7, 2001
Jun 7, 2001
855
856
857
858
859
860
861
*
* 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
862
863
864
* - 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
865
866
867
868
869
870
871
872
873
*
* 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
874
* all for you. Feel free to add more to the search path manually, too.
Jun 7, 2001
Jun 7, 2001
875
*
Jun 7, 2002
Jun 7, 2002
876
* \param organization Name of your company/group/etc to be used as a
Sep 26, 2001
Sep 26, 2001
877
878
* dirname, so keep it small, and no-frills.
*
Jun 7, 2002
Jun 7, 2002
879
* \param appName Program-specific name of your program, to separate it
Jun 7, 2001
Jun 7, 2001
880
881
* from other programs using PhysicsFS.
*
Jul 26, 2002
Jul 26, 2002
882
* \param archiveExt File extension used by your program to specify an
Jun 7, 2001
Jun 7, 2001
883
884
* 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
885
886
887
* 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
888
*
Jun 7, 2002
Jun 7, 2002
889
* \param includeCdRoms Non-zero to include CD-ROMs in the search path, and
Jun 7, 2001
Jun 7, 2001
890
891
892
893
894
895
896
* (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
897
*
Jun 7, 2002
Jun 7, 2002
898
* \param archivesFirst Non-zero to prepend the archives to the search path.
Jun 7, 2001
Jun 7, 2001
899
* Zero to append them. Ignored if !(archiveExt).
Sep 26, 2001
Sep 26, 2001
900
*
Jun 7, 2002
Jun 7, 2002
901
* \return nonzero on success, zero on error. Specifics of the error can be
Jul 6, 2001
Jul 6, 2001
902
* gleaned from PHYSFS_getLastError().
Jun 7, 2001
Jun 7, 2001
903
*/
Jan 29, 2010
Jan 29, 2010
904
905
906
907
908
PHYSFS_DECL int PHYSFS_setSaneConfig(const char *organization,
const char *appName,
const char *archiveExt,
int includeCdRoms,
int archivesFirst);
Jun 7, 2001
Jun 7, 2001
909
910
Dec 1, 2002
Dec 1, 2002
911
912
/* Directory management stuff ... */
Jun 7, 2001
Jun 7, 2001
913
/**
Jun 7, 2002
Jun 7, 2002
914
915
916
917
918
919
* \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
920
*
Jul 5, 2001
Jul 5, 2001
921
* So if you've got the write dir set to "C:\mygame\writedir" and call
Jun 7, 2001
Jun 7, 2001
922
* PHYSFS_mkdir("downloads/maps") then the directories
Jul 5, 2001
Jul 5, 2001
923
* "C:\mygame\writedir\downloads" and "C:\mygame\writedir\downloads\maps"
Jun 28, 2001
Jun 28, 2001
924
925
926
* 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
927
*
Jun 7, 2002
Jun 7, 2002
928
929
* \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
930
* gleaned from PHYSFS_getLastError().
Jun 7, 2002
Jun 7, 2002
931
932
*
* \sa PHYSFS_delete
Jun 7, 2001
Jun 7, 2001
933
*/
Jan 29, 2010
Jan 29, 2010
934
PHYSFS_DECL int PHYSFS_mkdir(const char *dirName);
Jun 7, 2001
Jun 7, 2001
935
936
937
/**
Jun 7, 2002
Jun 7, 2002
938
939
940
941
942
* \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
943
*
Jun 28, 2001
Jun 28, 2001
944
* A directory must be empty before this call can delete it.
Jun 7, 2001
Jun 7, 2001
945
*
Mar 25, 2002
Mar 25, 2002
946
947
948
* 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
949
* So if you've got the write dir set to "C:\mygame\writedir" and call
Jun 7, 2001
Jun 7, 2001
950
* PHYSFS_delete("downloads/maps/level1.map") then the file
Jul 5, 2001
Jul 5, 2001
951
* "C:\mygame\writedir\downloads\maps\level1.map" is removed from the
Jun 7, 2001
Jun 7, 2001
952
953
954
* physical filesystem, if it exists and the operating system permits the
* deletion.
*
Jun 7, 2001
Jun 7, 2001
955
956
957
958
* 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
959
960
961
962
* 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
963
964
* \param filename Filename to delete.
* \return nonzero on success, zero on error. Specifics of the error can be
Jun 7, 2001
Jun 7, 2001
965
966
* gleaned from PHYSFS_getLastError().
*/
Jan 29, 2010
Jan 29, 2010
967
PHYSFS_DECL int PHYSFS_delete(const char *filename);
Jun 7, 2001
Jun 7, 2001
968
969
970
/**
Jun 7, 2002
Jun 7, 2002
971
972
973
974
975
976
977
978
* \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
979
*
Jan 8, 2004
Jan 8, 2004
980
981
* So, if you look for "maps/level1.map", and C:\\mygame is in your search
* path and C:\\mygame\\maps\\level1.map exists, then "C:\mygame" is returned.
Jun 7, 2001
Jun 7, 2001
982
*
Jul 7, 2001
Jul 7, 2001
983
984
985
* 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
986
*
Mar 14, 2005
Mar 14, 2005
987
988
989
990
* If you specify a fake directory that only exists as a mount point, it'll
* be associated with the first archive mounted there, even though that
* directory isn't necessarily contained in a real archive.
*
Jun 7, 2002
Jun 7, 2002
991
992
* \param filename file to look for.
* \return READ ONLY string of element of search path containing the
Jun 28, 2001
Jun 28, 2001
993
994
* the file in question. NULL if not found.
*/
Jan 29, 2010
Jan 29, 2010
995
PHYSFS_DECL const char *PHYSFS_getRealDir(const char *filename);
Jun 28, 2001
Jun 28, 2001
996
997
998
/**
Jun 7, 2002
Jun 7, 2002
999
1000
* \fn char **PHYSFS_enumerateFiles(const char *dir)
* \brief Get a file listing of a search path's directory.