| /external/python/cpython3/Doc/library/ |
| D | os.path.rst | 1 :mod:`os.path` --- Common pathname manipulations
12 --------------
19 Unlike a Unix shell, Python does not do any *automatic* path expansions.
21 explicitly when an application desires shell-like path expansion. (See also
26 The :mod:`pathlib` module offers high-level path objects.
45 * :mod:`posixpath` for UNIX-style paths
64 Accepts a :term:`path-like object`.
72 from the Unix :program:`basename` program; where :program:`basename` for
77 Accepts a :term:`path-like object`.
82 Return the longest common sub-path of each pathname in the sequence
[all …]
|
| D | os.rst | 1 :mod:`os` --- Miscellaneous operating system interfaces
9 --------------
16 module, and for high-level file and directory handling see the :mod:`shutil`
21 * The design of all built-in operating system dependent modules of Python is
37 * On WebAssembly platforms ``wasm32-emscripten`` and ``wasm32-wasi``, large
41 (e.g. :func:`~os.nice`) are not available. Others like :func:`~os.getuid`
53 An alias for the built-in :exc:`OSError` exception.
64 system-dependent version information.
70 .. _os-filenames:
71 .. _filesystem-encoding:
[all …]
|
| D | intro.rst | 1 .. _library-intro:
13 define syntactic properties like the spelling and priorities of operators.)
15 The library also contains built-in functions and exceptions --- objects that can
24 Python, like printing a stack trace; some provide interfaces that are specific
26 provide interfaces that are specific to a particular application domain, like
32 This manual is organized "from the inside out:" it first describes the built-in
39 library. Of course, you don't *have* to read it like a novel --- you can also
45 :ref:`built-in-funcs`, as the remainder of the manual assumes familiarity with
56 * An "Availability: Unix" note means that this function is commonly found on
57 Unix systems. It does not make any claims about its existence on a specific
[all …]
|
| D | dbm.rst | 1 :mod:`dbm` --- Interfaces to Unix "databases"
5 :synopsis: Interfaces to various Unix "database" formats.
9 --------------
11 :mod:`dbm` is a generic interface to variants of the DBM database ---
13 slow-but-simple implementation in module :mod:`dbm.dumb` will be used. There
22 item --- the latter is used when :exc:`dbm.error` is raised.
28 available --- :mod:`dbm.gnu`, :mod:`dbm.ndbm` or :mod:`dbm.dumb` --- should
37 Accepts :term:`path-like object` for filename.
49 +---------+-------------------------------------------+
54 +---------+-------------------------------------------+
[all …]
|
| D | mmap.rst | 1 :mod:`mmap` --- Memory-mapped file support
5 :synopsis: Interface to memory-mapped files for Unix and Windows.
7 --------------
9 .. include:: ../includes/wasm-notavail.rst
11 Memory-mapped file objects behave like both :class:`bytearray` and like
14 module to search through a memory-mapped file. You can also change a single
19 A memory-mapped file is created by the :class:`~mmap.mmap` constructor, which is
20 different on Unix and on Windows. In either case you must provide a file
28 If you want to create a memory-mapping for a writable, buffered file, you
33 For both the Unix and Windows versions of the constructor, *access* may be
[all …]
|
| /external/okio/okio/src/commonMain/kotlin/okio/ |
| D | Path.kt | 8 * http://www.apache.org/licenses/LICENSE-2.0
24 * UNIX and Windows Paths
25 * ----------------------
27 * Paths follow different rules on UNIX vs. Windows operating systems. On UNIX operating systems
34 * ---------------------------
36 * * **Absolute paths** identify a location independent of any working directory. On UNIX, absolute
38 * first is a volume letter, a colon, and a backslash, like `C:\`. The second is called a
40 * ‘fully-qualified path’ is a synonym of ‘absolute path’.
49 * On Windows, each volume (like `A:\` and `C:\`) has its own current working directory. A path
50 * prefixed with a volume letter and colon but no slash (like `A:letter.doc`) is relative to the
[all …]
|
| /external/rust/crates/tokio/src/signal/windows/ |
| D | sys.rs | 10 pub(super) fn ctrl_break() -> io::Result<RxFuture> { in ctrl_break()
14 pub(super) fn ctrl_close() -> io::Result<RxFuture> { in ctrl_close()
18 pub(super) fn ctrl_c() -> io::Result<RxFuture> { in ctrl_c()
22 pub(super) fn ctrl_logoff() -> io::Result<RxFuture> { in ctrl_logoff()
26 pub(super) fn ctrl_shutdown() -> io::Result<RxFuture> { in ctrl_shutdown()
30 fn new(signum: u32) -> io::Result<RxFuture> { in new()
46 fn init() -> Self { in init()
58 fn event_info(&self, id: EventId) -> Option<&EventInfo> { in event_info()
85 fn init() -> Self { in init()
90 fn global_init() -> io::Result<()> { in global_init()
[all …]
|
| /external/python/cpython2/Doc/extending/ |
| D | windows.rst | 4 .. _building-on-windows:
13 Windows programmer learning to build Python extensions and the Unix programmer
14 interested in producing software which can be successfully built on both Unix
31 .. _win-cookbook:
37 are on Unix: use the :mod:`distutils` package to control the build process, or
40 is available in :ref:`distutils-index`. If you find you really need to do
45 .. _dynamic-linking:
47 Differences Between Unix and Windows
53 Unix and Windows use completely different paradigms for run-time loading of
57 In Unix, a shared object (:file:`.so`) file contains code to be used by the
[all …]
|
| /external/python/cpython3/Doc/extending/ |
| D | windows.rst | 4 .. _building-on-windows:
13 Windows programmer learning to build Python extensions and the Unix programmer
14 interested in producing software which can be successfully built on both Unix
31 .. _win-cookbook:
37 are on Unix: use the :mod:`distutils` package to control the build process, or
40 is available in :ref:`distutils-index`. If you find you really need to do
45 .. _dynamic-linking:
47 Differences Between Unix and Windows
53 Unix and Windows use completely different paradigms for run-time loading of
57 In Unix, a shared object (:file:`.so`) file contains code to be used by the
[all …]
|
| /external/okio/docs/ |
| D | file_system.md | 60 Okio’s `Path` class supports Windows-style (like `C:\autoexec.bat`) and UNIX-style paths
61 (like `/etc/passwd`). It supports manipulating Windows paths on UNIX, and UNIX paths on Windows.
67 * Linux: [man pages](https://www.kernel.org/doc/man-pages/)
68 * UNIX: [stdio.h](https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/stdio.h.html)
69 * Windows: [fileapi.h](https://docs.microsoft.com/en-us/windows/win32/api/fileapi/)
77 It exposes high-level operations like `atomicMove()` and `metadata` to get the OS to do all the work
91 * Paths that cannot be represented as UTF-8 strings are unsupported. The underlying APIs that Okio
119 * NodeJsFileSystem's `source()` and `sink()` cannot access UNIX pipes.
|
| /external/perfetto/include/perfetto/base/ |
| D | platform_handle.h | 8 * http://www.apache.org/licenses/LICENSE-2.0
28 // It should NOT be used to blanket-replace "int fd" in the codebase.
29 // Windows has two types of "handles", which, in UNIX-land, both map to int:
30 // 1. File handles returned by the posix-compatibility API like _open().
31 // These are just int(s) and should stay such, because all the posix-like API
33 // 2. Handles returned by old-school WINAPI like CreateFile, CreateEvent etc.
50 return h && h != reinterpret_cast<PlatformHandle>(-1); in IsValid()
62 // extra build edge for a one liner). This is really an alias for close() (UNIX)
64 // system headers like Windows.h through perfetto headers.
65 // Thre return value is always UNIX-style: 0 on success, -1 on failure.
|
| /external/python/cpython2/Doc/library/ |
| D | os.rst | 1 :mod:`os` --- Miscellaneous operating system interfaces
13 module, and for high-level file and directory handling see the :mod:`shutil`
18 * The design of all built-in operating system dependent modules of Python is
28 * An "Availability: Unix" note means that this function is commonly found on
29 Unix systems. It does not make any claims about its existence on a specific
32 * If not separately noted, all functions that claim "Availability: Unix" are
33 supported on Mac OS X, which builds on a Unix core.
47 An alias for the built-in :exc:`OSError` exception.
58 system-dependent version information.
64 .. _os-procinfo:
[all …]
|
| D | dbm.rst | 1 :mod:`dbm` --- Simple "database" interface
5 :platform: Unix
14 The :mod:`dbm` module provides an interface to the Unix "(n)dbm" library. Dbm
15 objects behave like mappings (dictionaries), except that keys and values are
20 compatibility interface, or the GNU GDBM compatibility interface. On Unix, the
29 Raised on dbm-specific errors, such as I/O errors. :exc:`KeyError` is raised for
30 general mapping errors like specifying an incorrect key.
47 +---------+-------------------------------------------+
52 +---------+-------------------------------------------+
55 +---------+-------------------------------------------+
[all …]
|
| D | othergui.rst | 1 .. _other-gui-packages:
6 Major cross-platform (Windows, Mac OS X, Unix-like) GUI toolkits are
15 good Python-specific reference documentation. There are also bindings to
20 PyQt is a :program:`sip`\ -wrapped binding to the Qt toolkit. Qt is an
22 available for Unix, Windows and Mac OS X. :program:`sip` is a tool
32 wxPython is a cross-platform GUI toolkit for Python that is built around
35 Windows, Mac OS X, and Unix systems by using each platform's native
36 widgets where ever possible, (GTK+ on Unix-like systems). In addition to
39 low-level device context drawing, drag and drop, system clipboard access,
40 an XML-based resource format and more, including an ever growing library
[all …]
|
| /external/freetype/docs/ |
| D | INSTALL.CROSS | 1 This document contains instructions on how to cross-build the FreeType
2 library on Unix systems, for example, building binaries for Linux/MIPS
4 file `INSTALL.UNIX' for required tools and the basic self-building
9 -----------------
11 For self-building the FreeType library on a Unix system, GNU Make
12 3.81 or newer is required. `INSTALL.UNIX' contains hints how to
15 The GNU C compiler to cross-build the target system is required.
16 Currently, using a non-GNU cross compiler is untested. The cross
20 the name `mips-ip22-linuxelf-gcc'.
22 A C compiler for a self-build is required also, to build a tool
[all …]
|
| /external/libpng/contrib/gregbook/ |
| D | README | 8 cross-platform demo programs that show how to use the libpng reference
10 a very simple example that that shows how a standard file-viewer might use
12 how a web browser might be written. wpng is a simple command-line program
17 Unix, OpenVMS, and 32-bit Windows. (Special thanks to Martin Zinser,
25 LICENSE terms of distribution and reuse (BSD-like or GNU GPL)
28 Makefile.unx Unix makefile
32 rpng-win.c Windows front end for the basic viewer
33 rpng-x.c X Window System (Unix, OpenVMS) front end
37 rpng2-win.c Windows front end for the progressive viewer
38 rpng2-x.c X front end for the progressive viewer
[all …]
|
| /external/swiftshader/third_party/llvm-subzero/lib/Support/Unix/ |
| D | README.txt | 1 llvm/lib/Support/Unix README
5 are common to two or more variants of UNIX. For example, the directory
6 structure underneath this directory could look like this:
8 Unix - only code that is truly generic to all UNIX platforms
9 Posix - code that is specific to Posix variants of UNIX
10 SUS - code that is specific to the Single Unix Specification
11 SysV - code that is specific to System V variants of UNIX
|
| /external/llvm/lib/Support/Unix/ |
| D | README.txt | 1 llvm/lib/Support/Unix README
5 are common to two or more variants of UNIX. For example, the directory
6 structure underneath this directory could look like this:
8 Unix - only code that is truly generic to all UNIX platforms
9 Posix - code that is specific to Posix variants of UNIX
10 SUS - code that is specific to the Single Unix Specification
11 SysV - code that is specific to System V variants of UNIX
|
| /external/swiftshader/third_party/llvm-10.0/llvm/lib/Support/Unix/ |
| D | README.txt | 1 llvm/lib/Support/Unix README
5 are common to two or more variants of UNIX. For example, the directory
6 structure underneath this directory could look like this:
8 Unix - only code that is truly generic to all UNIX platforms
9 Posix - code that is specific to Posix variants of UNIX
10 SUS - code that is specific to the Single Unix Specification
11 SysV - code that is specific to System V variants of UNIX
|
| /external/swiftshader/third_party/llvm-16.0/llvm/lib/Support/Unix/ |
| D | README.txt | 1 llvm/lib/Support/Unix README
5 are common to two or more variants of UNIX. For example, the directory
6 structure underneath this directory could look like this:
8 Unix - only code that is truly generic to all UNIX platforms
9 Posix - code that is specific to Posix variants of UNIX
10 SUS - code that is specific to the Single Unix Specification
11 SysV - code that is specific to System V variants of UNIX
|
| /external/freetype/builds/unix/ |
| D | unix.mk | 2 # FreeType 2 configuration rules for UNIX platforms
6 # Copyright (C) 1996-2023 by
15 # We need these declarations here since unix-def.mk is a generated file.
16 PLATFORM_DIR := $(TOP_DIR)/builds/unix
17 PLATFORM := unix
19 have_mk := $(wildcard $(OBJ_DIR)/unix-def.mk)
22 include $(OBJ_DIR)/unix-def.mk
23 include $(OBJ_DIR)/unix-cc.mk
25 include $(PLATFORM_DIR)/unix-def.mk
26 include $(PLATFORM_DIR)/unix-cc.mk
[all …]
|
| /external/libwebsockets/READMEs/ |
| D | README.jwt.md | 6 and JWT validation. All of the common algorithms like ES512 are supported
9 The build options needed are `-DLWS_WITH_JOSE=1` `-DLWS_WITH_GENCRYPTO=1`.
12 and finally a JWT-via http cookie level creation apis each building on top of
16 opportunity for implementation pitfalls like not validating alg carefully, or
19 doing, you can cut-and-paste out those implementations and create your own
24 Lws JWT uses mainly well-known fields
27 ---|---|---
28 iss|yes|Issuer, typically the domain like "warmcat.com"
29 aud|yes|Audience, typically a url path like "https://warmcat.com/sai"
30 iat|yes|Unix-time "Issued At"
[all …]
|
| /external/webp/doc/ |
| D | building.md | 8 nmake /f Makefile.vc CFG=release-static RTLIBCFG=static OBJDIR=output
11 the directory `output\release-static\(x64|x86)\bin` will contain the tools
12 cwebp.exe and dwebp.exe. The directory `output\release-static\(x64|x86)\lib`
17 ## Unix build using makefile.unix
22 make -f makefile.unix
26 library src/libwebp.a. No system-wide installation is supplied, as this is a
28 (see below). Please refer to makefile.unix for additional details and
35 On a Debian-like system the following should install everything you need for a
39 $ sudo apt-get install gcc make autoconf automake libtool
64 Note: A decode-only library, libwebpdecoder, is available using the
[all …]
|
| /external/okio/okio-fakefilesystem/src/commonMain/kotlin/okio/fakefilesystem/ |
| D | FakeFileSystem.kt | 8 * http://www.apache.org/licenses/LICENSE-2.0
42 * A fully in-memory file system useful for testing. It includes features to support writing
49 * -----------------
59 * Programs that do not attempt any of the above operations should work fine on both UNIX and
68 /** File system roots. Each element is a Directory and is created on-demand. */
87 * True to allow files to be moved even if they're currently open for read or write. UNIX file
93 * True to allow files to be deleted even if they're currently open for read or write. UNIX file
100 * systems typically allow files to replace empty directories; UNIX file systems do not.
106 * UNIX file systems permit this but the result may be undefined.
112 * UNIX file systems permit this but the result may be undefined.
[all …]
|
| /external/rust/crates/libc/ |
| D | CONTRIBUTING.md | 8 If you want to add your changes to v0.2, please submit them to the `libc-0.2` branch.
29 platforms of that level. For example, when adding a Unix API it should be added
30 to `src/unix/mod.rs`, but when adding a Linux-only API it should be added to
31 `src/unix/linux_like/linux/mod.rs`.
39 symbols list(s) found in the `libc-test/semver` directory. These lists keep
42 all supported Unixes it should be added to `unix.txt` list<sup>1</sup>,
53 <sup>1</sup>: Note that this list has nothing to do with any Unix or Posix
54 standard, it's just a list shared between all OSs that declare `#[cfg(unix)]`.
58 We have two automated tests running on [GitHub Actions](https://github.com/rust-lang/libc/actions):
60 1. [`libc-test`](https://github.com/gnzlbg/ctest)
[all …]
|