| commit | 0ec55f352cf3941e276e189d21923b10bbcab368 | |
| author | Sven Verdoolaege <sven.verdoolaege@gmail.com> | |
| Sat, 18 Mar 2023 16:07:44 +0000 (18 17:07 +0100) | ||
| committer | Sven Verdoolaege <sven.verdoolaege@gmail.com> | |
| Sat, 15 Apr 2023 12:39:06 +0000 (15 14:39 +0200) | ||
| tree | a73fa719c53606999c42c2eb86928718659574e7 | treesnapshot (tar.gz zip) |
| parent | 5c6979ce4a80e2a1bc35a9b3cf7048c3fb0712b1 | commitdiff |
always build Python interface if possible
That is, if the Python interface can be built, then build it
as part of "make all" and not just as part of "make check".
The C++ interfaces are already built as part of "make all"
because they are needed to build the C++ test programs,
while the Python interface is only need to run the Python test program.
Building the Python interface as part or "make all"
prepares for storing the interfaces in the git repository.
Signed-off-by: Sven Verdoolaege <sven.verdoolaege@gmail.com>
That is, if the Python interface can be built, then build it
as part of "make all" and not just as part of "make check".
The C++ interfaces are already built as part of "make all"
because they are needed to build the C++ test programs,
while the Python interface is only need to run the Python test program.
Building the Python interface as part or "make all"
prepares for storing the interfaces in the git repository.
Signed-off-by: Sven Verdoolaege <sven.verdoolaege@gmail.com>
| Makefile.am | diffblobblamehistory |