meson/test cases/frameworks/28 gir link order 2/meson-sample.h

#ifndef MESON_SAMPLE_H
#define MESON_SAMPLE_H

#include <glib-object.h>

G_BEGIN_DECLS

#define MESON_TYPE_SAMPLE (meson_sample_get_type())

G_DECLARE_FINAL_TYPE (MesonSample, meson_sample, MESON, SAMPLE, GObject)

MesonSample *meson_sample_new           (void);
void         meson_sample_print_message (MesonSample *self);

G_END_DECLS

#endif /* MESON_SAMPLE_H */
gnome: make sure the target build directory is passed first for linking determine_rpath_dirs() can return paths to external dependencies not in the build dir and passing them first as a link path leads to g-ir-scanner for example linking against the already installed library instead of the just built one. This was reported in g-i: https://gitlab.gnome.org/GNOME/gobject-introspection/issues/272 and comes up quite often when a library adds some new symbols which aren't present in the system library, which then makes linking fail. The first place where the order is changed is _scan_gir_targets(), which looks like an unintentional change in the refactoring in 8377ea45aa61efbe8e1a75b74 The second place in _get_link_args() has always been that way and only the rpath order is changed, but it looks to me as if the same rules should apply here too. 6 years ago			`#ifndef MESON_SAMPLE_H`
			`#define MESON_SAMPLE_H`

			`#include <glib-object.h>`

			`G_BEGIN_DECLS`

			`#define MESON_TYPE_SAMPLE (meson_sample_get_type())`

			`G_DECLARE_FINAL_TYPE (MesonSample, meson_sample, MESON, SAMPLE, GObject)`

			`MesonSample *meson_sample_new (void);`
			`void meson_sample_print_message (MesonSample *self);`

			`G_END_DECLS`

			`#endif /* MESON_SAMPLE_H */`