blob: aa703d9419280bc8e41c676985ea6b62006cd3fe (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
|
.. _project-file:
********************
Binding Project File
********************
Instead of directing the Generator behavior via command line, the binding
developer can write a text project file describing the same information, and
avoid the hassle of a long stream of command line arguments.
.. _project-file-structure:
The project file structure
==========================
Here follows a comprehensive example of a generator project file.
.. code-block:: ini
[generator-project]
generator-set = path/to/generator/CHOICE_GENERATOR
header-file = DIR/global.h" />
typesystem-file = DIR/typesystem_for_your_binding.xml
output-directory location="OUTPUTDIR" />
include-path = path/to/library/being/wrapped/headers/1
include-path = path/to/library/being/wrapped/headers/2
typesystem-path = path/to/directory/containing/type/system/files/1
typesystem-path = path/to/directory/containing/type/system/files/2
enable-parent-ctor-heuristic
Project file tags
=================
The generator project file tags are in direct relation to the
:ref:`command line arguments <command-line>`. All of the current command line
options provided by |project| were already seen on the
:ref:`project-file-structure`, for new command line options provided by
additional generator modules (e.g.: qtdoc, Shiboken) could also be used in the
generator project file following simple conversion rules.
For tags without options, just write as an empty tag without any attributes.
Example:
.. code-block:: bash
--BOOLEAN-ARGUMENT
becomes
.. code-block:: ini
BOOLEAN-ARGUMENT
and
.. code-block:: bash
--VALUE-ARGUMENT=VALUE
becomes
.. code-block:: ini
VALUE-ARGUMENT = VALUE
|
