Skip to content
GitLab
Select Git revision
Find file Blame History Permalink
  • Alex Blasche's avatar
    Make bluez compile test pass again · 7d5ff0b7
    Alex Blasche authored 
    
The compiler error is:

In file included from main.cpp:29:0:
main.cpp: In function 'int main()'
main.cpp:33:11: error: taking address of temporary [-fpermissive]
     bacmp(BDADDR_ANY, BDADDR_NONE);
           ^
main.cpp:33:23: error: 'BDADDR_NONE' was not declared in this scope
     bacmp(BDADDR_ANY, BDADDR_NONE);

BDADDR_NONE only exists in Linux iBluetooth kernel headers but not in the
Bluez project headers. Furthermore the usage of the BDADDR_* defines
is known to trigger -fpermissive violations. For the prupose of this test
fpermissive is not relevant as the test is never executed and the focus
is in checking the existence of the very same defines.

Change-Id: I56db5406ec91fdd5e7998cac4900ee9f9b628c00
Reviewed-by: default avatarTimur Pocheptsov <timur.pocheptsov@qt.io>
Reviewed-by: default avatarJérôme Duval <jerome.duval@gmail.com>
    7d5ff0b7
usage.dox 10.90 KiB
1 
/*!\page usage Usage
2
3 
    The vpx Multi-Format codec SDK provides a unified interface amongst its
4 
    supported codecs. This abstraction allows applications using this SDK to
5 
    easily support multiple video formats with minimal code duplication or
6 
    "special casing." This section describes the interface common to all codecs.
7 
    For codec-specific details, see the \ref codecs page.
8
9 
    The following sections are common to all codecs:
10 
    - \ref usage_types
11 
    - \ref usage_features
12 
    - \ref usage_init
13 
    - \ref usage_errors
14
15 
    Fore more information on decoder and encoder specific usage, see the
16 
    following pages:
17 
    \if decoder - \subpage usage_decode \endif
18 
    \if decoder - \subpage usage_encode \endif
19
20 
    \section usage_types Important Data Types
21 
    There are two important data structures to consider in this interface.
22
23 
    \subsection usage_ctxs Contexts
24 
    A context is a storage area allocated by the calling application that the
25 
    codec may write into to store details about a single instance of that codec.
26 
    Most of the context is implementation specific, and thus opaque to the
27 
    application. The context structure as seen by the application is of fixed
28 
    size, and thus can be allocated eith with automatic storage or dynamically
29 
    on the heap.
30
31 
    Most operations require an initialized codec context. Codec context
32 
    instances are codec specific. That is, the codec to be used for the encoded
33 
    video must be known at initialization time. See #vpx_codec_ctx_t for further
34 
    information.
35
36 
    \subsection usage_ifaces Interfaces
37 
    A codec interface is an opaque structure that controls how function calls
38 
    into the generic interface are dispatched to their codec-specific
39 
    implementations. Applications \ref MUSTNOT attempt to examine or override
40 
    this storage, as it contains internal implementation details likely to
41 
    change from release to release.
42
43 
    Each supported codec will expose an interface structure to the application
44 
    as an <code>extern</code> reference to a structure of the incomplete type
45 
    #vpx_codec_iface_t.
46
47 
    \section usage_features Features
48 
    Several "features" are defined that are optionally implemented by codec
49 
    algorithms. Indeed, the same algorithm may support different features on
50 
    different platforms. The purpose of defining these features is that when
51 
    they are implemented, they conform to a common interface. The features, or
52 
    capabilities, of an algorithm can be queried from it's interface by using
53 
    the vpx_codec_get_caps() method. Attempts to invoke features not supported
54 
    by an algorithm will generally result in #VPX_CODEC_INCAPABLE.
55
56 
    Currently defined features available in both encoders and decoders include:
57 
    - \subpage usage_xma
58
59 
    \if decoder
60 
    Currently defined decoder features include:
61 
    - \ref usage_cb
62 
    - \ref usage_postproc
63 
    \endif
64
65 
    \section usage_init Initialization
66 
    To initialize a codec instance, the address of the codec context
67 
    and interface structures are passed to an initialization function. Depending
68 
    on the \ref usage_features that the codec supports, the codec could be
69 
    initialized in different modes. Most notably, the application may choose to
70 
    use \ref usage_xma mode to gain fine grained control over how and where