| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For Visual Studio builds, it is likely that we specify a specific Python
installation as there may well be multiple Python installations, but
_giscanner.pyd gets tied to the particular Python DLL that it was built
with. So, we cannot just use /usr/bin/env python3 in such a case on
Visual Studio, but instead we use the full path to the Python executable
in the shebang so that the correct Python installation is used, when
running the installed scripts. This is necessary as Meson could bump
the Python version it requires but _giscanner.pyd could not be used on
the newer Python that is required due to differences in the Python
version and the CRT Python itself is linked to, for instance.
We continue to use /usr/bin/env python[2|3] for other builds.
|
|
|
|
|
|
|
|
|
| |
* This adds a new dependency on autoconf-archive.
* Pass WARN_CFLAGS/WARN_LDFLAGS/WARN_SCANNERFLAGS to everything we control the source of
* Disables all warning flags which make the build error out for now, we'll re-enable them
in followup commits.
* AX_COMPILER_FLAGS is used with the release flag always on so we don't get
-Werror by default.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Various distributions (mainly RPM based so far) make use of automatic
dependencies extracted from typelib files (they can require other typelibs
and also shared libraries)
Current features
* Print used shared libraries
* Print used typelib dependencies
Based-on-patch-by: Dominique Leuenberger <dimstar@opensuse.org>
Reference: https://bugzilla.gnome.org/show_bug.cgi?id=665672
Reviewed-by: Colin Walters <walters@verbum.org>
Signed-off-by: Dominique Leuenberger <dimstar@opensuse.org>
Signed-off-by: Igor Gnatenko <ignatenko@redhat.com>
|
|
|
|
|
|
| |
g-ir-annotation-tool, g-ir-doc-tool and g-ir-scanner where identical
except for the module and function being invoked.
Avoid code duplication and generate these from a common template.
|
| |
|
|
|
|
|
|
| |
use TOOL_SUBSTITUTIONS like the others, to fix an unsubstitued @datarootdir@ in g-ir-doc-tool
https://bugzilla.gnome.org/show_bug.cgi?id=659649
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=625494
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=655437
|
|
|
|
|
| |
Generating Python source code is problematic for srcdir != builddir;
steal a the trick of putting global data in __builtins__ from jhbuild.
|
|
|
|
|
| |
This should better avoid them being exported. Rename
girepository-parser.la to girepository-internals.la for clarity.
|
|
|
|
|
|
| |
It seems in some cases (Debian libtool) we get an injected rpath
first for the jhbuild root, which screws us over since we need
the libraries from .libs.
|
|
|
|
|
| |
On Debian, libtool won't pull in dependencies from internal libraries when
linking.
|
|
|
|
| |
girepository only explicitly deps on GObject, so this is correct.
|
|
This is cleaner and faster, and prepares us better for an incoming
import of CMPH.
|