| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Formerly, trying to build gi/Foo-1.0.gir resulted in namespace being set to "gi/Foo"
Trying to build g-i/Foo-1.0.gir was even setting it to "g"
This fixes this behaviour by only considerating the filename without dirs.
Btw, ensure that the directory exists
Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
https://bugzilla.gnome.org/show_bug.cgi?id=665276
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
line arguments.
This continues to reuse the LIBTOOL variable from automake if it's set,
but works around some MSYS weirdness: When running g-ir-scanner, MSYS
changes a command-line argument --libtool="/bin/sh ../../libtool" into
--libtool=c:/opt/msys/1.0/bin/libtool. So just use sh.exe without path
because we already "know" where the libtool configure produced is.
https://bugzilla.gnome.org/show_bug.cgi?id=620566
|
| | |
|
| |
|
|
|
| |
Convert slashes to underscores in _gir_name so that non-recursive builds can
use Makefile.introspection. Closes: bgo#628594
|
| |
|
|
| |
This new variable maps to --pkg-export.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
When debugging the dumper, it's extremely useful to be able
to see the argument it's passing to the compiler/linker.
This patch makes g-ir-scanner work the same way as libtool basically;
we default to printing out stuff, and add a --quiet option.
The Makefile.introspection handles passing --quiet automatically.
https://bugzilla.gnome.org/show_bug.cgi?id=622751
|
| |
|
|
|
|
|
| |
We need our just-built library path to override what we have
from pkg-config.
https://bugzilla.gnome.org/show_bug.cgi?id=605156
|
| |
|
|
|
|
|
|
|
|
| |
This allows specifying LDFLAGS for the introspection scanner.
LDFLAGS are currently just appended to the CFLAGS as the current scanner
doesn't make the difference between both, but it looked wrong to include
LDFLAGS in the middle of CFLAGS for g-ir-scanner.
https://bugzilla.gnome.org/show_bug.cgi?id=620875
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the .gir-building rule, use "$^" to refer to the source files,
since that automatically looks in both $(srcdir) and $(builddir). This
is particularly important since certain generated files will be in
$(builddir) when building from git, but in $(srcdir) when building
from tarballs
If you were previously prefixing $(srcdir) to the Foo_gir_FILES
members by hand, you should stop now.
(Also, removed the dependencies on $(INTROSPECTION_SCANNER) and
$(INTROSPECTION_COMPILER) for the .gir/.typelib rules, since the
scanner one was broken anyway, and we don't have that kind of
dependency for other rules (eg, making .o files depend on
/usr/bin/gcc).)
https://bugzilla.gnome.org/show_bug.cgi?id=616425
|
| |
|
|
| |
Instead use the path from configure in the example.
|
| |
|
|
|
| |
We should not require AM_DEFAULT_VERBOSITY to be present, workaround
that fact
|
| |
|
|
|
| |
This is only supported with automake 1.11 or newer, older versions
should default to showing nothing for now.
|
| |
|
|
|
| |
It's useful to be able to include the makefile without
having introspection enabled.
|
| |
|
|
|
| |
As it breaks when including the makefile when using
an absolute path.
|
|
|
This will make it easier for third-party projects to use
introspection by having easy make rules.
|
