Lines Matching full:the
4 We have written a script that will read the header files in LVGL and outputs a more friendly JSON f…
5 This is done so that bindings that generate code automatically will have an easy way to collect the…
6 without having to reinvent the wheel. The JSON data format has already made libraries for reading t…
9 The script in order to run does have some requirements.
12 - Pycparser >= 2.21: Python Library for reading the preprocessor ouotput from the C compiler
15 - Doxygen: used to read the docstrings from the header files.
18 There are several options when running the script. They are as follows
23 - `--develop`: leaves the temporary folder in place.
26 to use the script
33 or if you want to run a subprocess from inside of a generation script and read the output from stdo…
40 The JSON data is broken apart into a couple of main categories.
52 Those categories are the element names undert the root of the JSON data.
53 The value for each categry is an array of JSON elements. There is a bit of
54 nesting with the elements in the arrays and I have created "json_types" that
57 The different "json_types" are as follows:
59 - ``"array"``: The array type is used to identify arrays.
62 - ``"dim"``: number of items in the array
65 - ``"name"``: the name of the data type
69 It is used in the ``"fields"`` array of the ``"struct"`` and ``"union"`` JSON types.
72 - ``"name"``: The name of the field.
73 - ``"type"``: This contains the type information for the field. Check the
75 - ``"bitsize"``: The number of bits the field has or ``null``
83 - ``"name"``: The name of the argument/parameter.
84 - ``"type"``: This contains the type information for the field. Check the
94 - ``"name"``: The name of the formard declaration.
95 - ``"type"``: This contains the type information for the field. Check the
105 - ``"name"``: The name of the function pointer.
106 - ``"type"``: This contains the return type information for the function pointer.
108 - ``"args"``: array of ``"arg"`` Widgets. This describes the function arguments/parameters.
115 - ``"name"``: The name of the variable.
116 - ``"type"``: This contains the type information for the field. Check the
131 This tells you that the type is a basic or primitive C type.
135 - ``"name"``: The name of the primitive type.
141 - ``"name"``: The name of the enumeration group/type.
142 - ``"type"``: This contains the type information for the enumeration group.
144 type as the type for the members of this enumeration group. Check the
145 enumeration members type to get the correct type.
151 the ``"members"`` field of an ``"enum"`` JSON type
154 - ``"name"``: The name of the enumeration.
155 - ``"type"``: This contains the type information for the enum member.
156 This gets a bit tricky because the type specified in here is not always
157 going to be an "int". It will usually point to an lvgl type and the type
158 of the lvgl type can be found in the ``"typedefs"`` section.
160 - ``"value"``: the enumeration member/item's value
164 This tells you that the type is an LVGL data type.
167 - ``"name"``: The name of the type.
174 - ``"name"``: The name of the structure.
175 - ``"type"``: This contains the primitive type information for the structure.
184 - ``"name"``: The name of the union.
185 - ``"type"``: This contains the primitive type information for the union.
193 statically added to a binding. It is more for collecting the docstrings than
197 - ``"name"``: The name of the macro.
201 - ``"ret_type"``: return type from a function. This is only going to be seen in the ``"type"``
205 - ``"type"``: This contains the type information for the field. Check the
213 - ``"name"``: The name of the function.
214 - ``"type"``: This contains the type information for the return value.
216 - ``"args"``: array of ``"arg"`` json types. This describes the function arguments/parameters.
220 type levels beneith this. This tells us that the type is from the C stdlib.
223 - ``"name"``: The name of the type.
228 an adjustment made to the script. Please open an issue and let us know if you see this type.
231 - ``"name"``: The name of the type.
235 - ``"pointer"``: This is a wrapper object to let you know that the type you
239 - ``"type"``: This contains the type information for the pointer. Check the
247 - ``"name"``: The name of the typedef.
248 - ``"type"``: This contains the type information for the field. Check the
255 Here is an example of what the output will look like.