Link and run the dumper program firstly against the build of ATK from the
same tarball,then linking to the other dependent libraries which this build
of ATK was built against before finally trying to link and run against
other existing builds.
This is especially important for unstable releases, as APIs are often added
and dependent upon during development cycles.
@-echo Generating Atk-$(APIVERSION).gir...
@set CC=$(CC)
@set PYTHONPATH=$(BASEDIR)\lib\gobject-introspection
- @set PATH=win32\vs$(VSVER)\$(CFG)\$(PLAT)\bin;$(PATH);$(MINGWDIR)\bin
+ @set PATH=win32\vs$(VSVER)\$(CFG)\$(PLAT)\bin;$(BASEDIR)\bin;$(PATH);$(MINGWDIR)\bin
@set PKG_CONFIG_PATH=$(PKG_CONFIG_PATH)
+ @set LIB=win32\vs$(VSVER)\$(CFG)\$(PLAT)\bin;$(BASEDIR)\lib;$(LIB)
$(PYTHON2) $(G_IR_SCANNER) --verbose -I.. --add-include-path=.. \
--namespace=Atk --nsversion=$(APIVERSION) --include=GObject-2.0 \
--no-libtool --pkg=glib-2.0 --library=$(DLLNAME) \