Red Hat ENTERPRISE LINUX 3 - DEVELOPER TOOLS GUIDE Uživatelská příručka Strana 32
- Strana / 100
- Tabulka s obsahem
- KNIHY
Hodnocené. / 5. Na základě hodnocení zákazníků
Chapter 3. Libraries and Runtime Support
22
This type of compatibility is defined by conformance with specified Application Binary Interfaces
(ABIs).
3.2.1. API Compatibility
Source compatibility enables a body of application source code to be compiled and operate correctly
on multiple instances of an operating environment, across one or more hardware architectures, as
long as the source code is compiled individually for each specific hardware architecture.
Source compatibility is defined by an Application Programming Interface (API), which is a set of
programming interfaces and data structures provided to application developers. The programming
syntax of APIs in the C programming language are defined in header files. These header files
specify data types and programmatic functions. They are available to programmers for use in their
applications, and are implemented by the operating system or libraries. The syntax of APIs are
enforced at compile time, or when the application source code is compiled to produce executable
binary objectcode.
APIs are classified as:
• De facto standards not formally specified but implied by a particular implementation.
• De jure standards formally specified in standards documentation.
In all cases, application developers should seek to ensure that any behavior they depend on is
described in formal API documentation, so as to avoid introducing dependencies on unspecified
implementation specific semantics or even introducing dependencies on bugs in a particular
implementation of an API. For example, new releases of the GNU C library are not guaranteed to be
compatible with older releases if the old behavior violated a specification.
Red Hat Enterprise Linux by and large seeks to implement source compatibility with a variety of
de jure industry standards developed for Unix operating environments. While Red Hat Enterprise
Linux does not fully conform to all aspects of these standards, the standards documents do provide
a defined set of interfaces, and many components of Red Hat Enterprise Linux track compliance with
them (particularly glibc, the GNU C Library, and gcc, the GNU C/C++/Java/Fortran Compiler). There
are and will be certain aspects of the standards which are not implemented as required on Linux.
3.2.2. ABI Compatibility
Binary compatibility enables a single compiled binary to operate correctly on multiple instances of
an operating environment that share a common hardware architecture (whether that architecture
support is implemented in native hardware or a virtualization layer), but a different underlying software
architecture.
Binary compatibility is defined by an Application Binary Interface (ABI). The ABI is a set of runtime
conventions adhered to by all tools which deal with a compiled binary representation of a program.
Examples of such tools include compilers, linkers, runtime libraries, and the operating system itself.
The ABI includes not only the binary file formats, but also the semantics of library functions which are
used by applications.
3.2.3. Policy
Ideally you should rebuild and repackage your applications for each major release. This will allow you
take advantage of new optimizations in the compiler, as well as new features available in the latest
tools.
However, we understand there are times when it is useful to build one set of binaries that can be
deployed on multiple major releases at once. This is especially useful with old code bases that are not
- Red Hat Enterprise Linux 6 1
- Developer Guide 1
- Enterprise Linux 6 3
- Edition 0 3
- 1. Document Conventions 7
- 1.2. Pull-quote Conventions 8
- 1.3. Notes and Warnings 9
- 2.1. Do You Need Help? 9
- 2.2. We Need Feedback! 10
- Introduction to Eclipse 11
- 1.2. Help In Eclipse 13
- 1.3. Development Toolkits 15
- Environment (IDE) 17
- 2.2. Useful Hints 21
- 2.2.2. libhover Plug-in 27
- 2.2.2.1. Setup and Usage 28
- Libraries and Runtime Support 31
- 3.2.1. API Compatibility 32
- 3.2.2. ABI Compatibility 32
- 3.2.3. Policy 32
- 3.2.4. Static Linking 33
- 3.3.1. The GNU C Library 33
- std::vector 37
- elements in any order 37
- 3.3.3. Boost 38
- 3.3.3.1. Boost Updates 39
- 3.3.3.2. Boost Documentation 40
- 3.3.4. Qt 41
- 3.3.4.2. Qt Creator 42
- 3.3.5.1. KDE4 Architecture 42
- 3.3.6. Python 44
- 3.3.7. Java 45
- 3.3.8. Ruby 46
- 3.3.9. Perl 47
- 3.3.9.3. Perl Documentation 48
- Compiling and Building 49
- 4.1.2. Language Compatibility 50
- 4.1.6. Running GCC 53
- 4.1.6.1. Simple C Usage 54
- 4.1.6.2. Simple C++ Usage 54
- 4.2. Distributed Compiling 60
- 4.3. Autotools 60
- 4.3.2. Configuration Script 61
- Debugging 63
- 5.2.1. Simple GDB 64
- 5.2.2. Running GDB 65
- 5.2.4. Forked Execution 68
- 5.2.5. Threads 68
- 5.2.7. GDB Documentation 68
- 5.4. Python Pretty-Printers 69
- Highly Customizable 70
- Easy to Learn 70
- Profiling 71
- 6.2. Valgrind 72
- 6.2.2. Using Valgrind 73
- 6.3. OProfile 74
- 6.3.2. Using OProfile 75
- 6.4. SystemTap 76
- Unprivileged Users) 78
- 6.5. Eclipse-Callgraph 79
- Chapter 6. Profiling 80
- 6.5.2. The Callgraph View 81
- Go to Code 84
- 6.6.1. Perf Tool Commands 85
- 6.6.2. Using Perf 85
- 6.7. ftrace 87
- 6.7.2. ftrace Documentation 88
- Appendix A. Revision History 89
Související produkty a manuály pro Operační systémy Red Hat ENTERPRISE LINUX 3 - DEVELOPER TOOLS GUIDE
(24 stránky)Advent Vídeo del coche manuales de usuario
La lista de productos de Advent Vídeo del coche contiene 9 manuales de usuario para 9 seleccionados. Todas las guías de usuario en pdf están disponibles para descargar o ver en línea.
| Modelos | Tipo de documento |
|---|---|
| 128-8567 | |
| ADV10A | |
| AMM12N | |
| TOCLJ-OE100 | |
| TOCLS-OE100 | |
| VIDEO CROBILE ADV49 | |
| VIDEO MOBILE ADV38 |
© 2020, manymanuals.cz. Všechna práva vyhrazena. | 0.032 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Komentáře k této Příručce