package/gobject-introspection: new package
GObject introspection is a middleware layer between C
libraries (using GObject) and language bindings. The C library
can be scanned at compile time and generate a metadata file,
in addition to the actual native C library. Then at runtime,
language bindings can read this metadata and automatically
provide bindings to call into the C library.
There's an XML format called GIR used by GObject-Introspection.
The purpose of it is to provide a standard structure to access the complete
available API that a library or other unit of code exports. It's
language-agnostic using namespaces to separate core, language, or
library-specific functionality.
Cross-compiling gobject-introspection is not an easy task. The main issue is
that in the process of creating the XML files, gobject-introspection must first
run and scan the binary, which, if the binary is cross-compiled, would not
typically be possible from the host system.
Because of this limitation, we use several wrappers to call instead first out
qemu, which runs the native scanner to create the binaries.
There are seven total patches and four different wrapper files needed to
successfully cross-compile and run this package, many of them are from
open-embedded, but one of them is of my own doing.
1) Revert a previous, incomplete attempt at adding cross-compiling support.
2) Add support for cross-compiling with meson.
3) Disable tests.
4) Add an option to use a binary wrapper; this patch will force giscanner to
use a wrapper executable to run binaries it's producing, instead of
attempting to run them from the host.
5) Add an option to use an LDD wrapper, again, useful for cross-compiled
environments.
6) Add a --lib-dirs-envar option to pass to giscanner. (See patch for details.)
7) Add rpath-links to ccompiler: when passing the PACKAGE_GIR_EXTRA_LIBS_PATH
to the ccompiler.py script, ccompiler.py needs to add -Wl,-rpath-link to the
environment for the package to correctly link against the passed on paths.
8) Ignore error return codes from ldd-wrapper because prelink-rtld returns 127
when it can't find a library, which breaks subprocess.check_output().
Signed-off-by: Adam Duskett <Aduskett@gmail.com>
Tested-by: Yegor Yefremov <yegorslists@googlemail.com>
Tested-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
[yann.morin.1998@free.fr:
- host-prelink-cross has no Kconfig entry
- reorder dependencies for arch deps first
]
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-02-11 17:34:04 +01:00
|
|
|
config BR2_PACKAGE_GOBJECT_INTROSPECTION
|
|
|
|
|
bool "gobject-introspection"
|
|
|
|
|
depends on BR2_USE_MMU # python3, libglib2
|
|
|
|
|
depends on BR2_PACKAGE_HOST_QEMU_ARCH_SUPPORTS
|
|
|
|
|
# While gcc 4.8 might be compatible with gobject-introspection,
|
|
|
|
|
# The autobuilders use some toolchains from codesourcery which
|
|
|
|
|
# have gcc 4.8 and a very old version of glibc, which will cause
|
|
|
|
|
# compile errors with locale.c. As such, require 4.9 until this
|
|
|
|
|
# can be verified.
|
|
|
|
|
depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_9
|
|
|
|
|
depends on BR2_TOOLCHAIN_USES_GLIBC
|
2020-02-22 22:31:42 +01:00
|
|
|
# gobject-introspection does not require python3 to run on the
|
|
|
|
|
# target; however, because the tools run in a qemu wrapper, a
|
|
|
|
|
# cross-compiled python3 must be installed to staging. As there
|
|
|
|
|
# is no current mechanism to tell Buildroot only to install
|
|
|
|
|
# python to staging, then python must also be installed
|
|
|
|
|
# unconditionally to the target when building
|
|
|
|
|
# gobject-introspection.
|
|
|
|
|
depends on BR2_PACKAGE_PYTHON3
|
package/gobject-introspection: new package
GObject introspection is a middleware layer between C
libraries (using GObject) and language bindings. The C library
can be scanned at compile time and generate a metadata file,
in addition to the actual native C library. Then at runtime,
language bindings can read this metadata and automatically
provide bindings to call into the C library.
There's an XML format called GIR used by GObject-Introspection.
The purpose of it is to provide a standard structure to access the complete
available API that a library or other unit of code exports. It's
language-agnostic using namespaces to separate core, language, or
library-specific functionality.
Cross-compiling gobject-introspection is not an easy task. The main issue is
that in the process of creating the XML files, gobject-introspection must first
run and scan the binary, which, if the binary is cross-compiled, would not
typically be possible from the host system.
Because of this limitation, we use several wrappers to call instead first out
qemu, which runs the native scanner to create the binaries.
There are seven total patches and four different wrapper files needed to
successfully cross-compile and run this package, many of them are from
open-embedded, but one of them is of my own doing.
1) Revert a previous, incomplete attempt at adding cross-compiling support.
2) Add support for cross-compiling with meson.
3) Disable tests.
4) Add an option to use a binary wrapper; this patch will force giscanner to
use a wrapper executable to run binaries it's producing, instead of
attempting to run them from the host.
5) Add an option to use an LDD wrapper, again, useful for cross-compiled
environments.
6) Add a --lib-dirs-envar option to pass to giscanner. (See patch for details.)
7) Add rpath-links to ccompiler: when passing the PACKAGE_GIR_EXTRA_LIBS_PATH
to the ccompiler.py script, ccompiler.py needs to add -Wl,-rpath-link to the
environment for the package to correctly link against the passed on paths.
8) Ignore error return codes from ldd-wrapper because prelink-rtld returns 127
when it can't find a library, which breaks subprocess.check_output().
Signed-off-by: Adam Duskett <Aduskett@gmail.com>
Tested-by: Yegor Yefremov <yegorslists@googlemail.com>
Tested-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
[yann.morin.1998@free.fr:
- host-prelink-cross has no Kconfig entry
- reorder dependencies for arch deps first
]
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-02-11 17:34:04 +01:00
|
|
|
select BR2_PACKAGE_HOST_QEMU
|
|
|
|
|
select BR2_PACKAGE_HOST_QEMU_LINUX_USER_MODE
|
|
|
|
|
select BR2_PACKAGE_LIBFFI
|
|
|
|
|
select BR2_PACKAGE_LIBGLIB2
|
|
|
|
|
select BR2_PACKAGE_ZLIB
|
|
|
|
|
help
|
|
|
|
|
GObject introspection is a middleware layer between C
|
|
|
|
|
libraries (using GObject) and language bindings. The C library
|
|
|
|
|
can be scanned at compile time and generate a metadata file,
|
|
|
|
|
in addition to the actual native C library. Then at runtime,
|
|
|
|
|
language bindings can read this metadata and automatically
|
|
|
|
|
provide bindings to call into the C library.
|
|
|
|
|
|
|
|
|
|
https://wiki.gnome.org/action/show/Projects/GObjectIntrospection
|
|
|
|
|
|
2020-02-22 22:31:42 +01:00
|
|
|
comment "gobject-introspection needs python3"
|
|
|
|
|
depends on !BR2_PACKAGE_PYTHON3
|
|
|
|
|
|
package/gobject-introspection: new package
GObject introspection is a middleware layer between C
libraries (using GObject) and language bindings. The C library
can be scanned at compile time and generate a metadata file,
in addition to the actual native C library. Then at runtime,
language bindings can read this metadata and automatically
provide bindings to call into the C library.
There's an XML format called GIR used by GObject-Introspection.
The purpose of it is to provide a standard structure to access the complete
available API that a library or other unit of code exports. It's
language-agnostic using namespaces to separate core, language, or
library-specific functionality.
Cross-compiling gobject-introspection is not an easy task. The main issue is
that in the process of creating the XML files, gobject-introspection must first
run and scan the binary, which, if the binary is cross-compiled, would not
typically be possible from the host system.
Because of this limitation, we use several wrappers to call instead first out
qemu, which runs the native scanner to create the binaries.
There are seven total patches and four different wrapper files needed to
successfully cross-compile and run this package, many of them are from
open-embedded, but one of them is of my own doing.
1) Revert a previous, incomplete attempt at adding cross-compiling support.
2) Add support for cross-compiling with meson.
3) Disable tests.
4) Add an option to use a binary wrapper; this patch will force giscanner to
use a wrapper executable to run binaries it's producing, instead of
attempting to run them from the host.
5) Add an option to use an LDD wrapper, again, useful for cross-compiled
environments.
6) Add a --lib-dirs-envar option to pass to giscanner. (See patch for details.)
7) Add rpath-links to ccompiler: when passing the PACKAGE_GIR_EXTRA_LIBS_PATH
to the ccompiler.py script, ccompiler.py needs to add -Wl,-rpath-link to the
environment for the package to correctly link against the passed on paths.
8) Ignore error return codes from ldd-wrapper because prelink-rtld returns 127
when it can't find a library, which breaks subprocess.check_output().
Signed-off-by: Adam Duskett <Aduskett@gmail.com>
Tested-by: Yegor Yefremov <yegorslists@googlemail.com>
Tested-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
[yann.morin.1998@free.fr:
- host-prelink-cross has no Kconfig entry
- reorder dependencies for arch deps first
]
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-02-11 17:34:04 +01:00
|
|
|
comment "gobject-introspection needs a glibc toolchain, gcc >= 4.9"
|
|
|
|
|
depends on BR2_USE_MMU
|
|
|
|
|
depends on BR2_PACKAGE_HOST_QEMU_ARCH_SUPPORTS
|
|
|
|
|
depends on !BR2_TOOLCHAIN_USES_GLIBC || \
|
|
|
|
|
!BR2_TOOLCHAIN_GCC_AT_LEAST_4_9
|