yes I'm speaking about vapigen
after checkin: 7a4f0befbd58286a69367ba78d16187da25724f7
build: Make building vapigen non-optional
it is not more possible to use --disable-vapigen
>>> miki@HP-EliteBook-840-G1:~/Develop/vala (master) $ git log -1
>>> commit 3658f709ba698bf6fcfb989c193a5451ff5a147d
>>> Author: Jürg Billeter <j...@bitron.ch>
>>> Date: Mon Sep 15 18:37:11 2014 +0200
>>>
>>> Release 0.25.4
>>> miki@HP-EliteBook-840-G1:~/Develop/vala (master) $ ./autogen.sh
--disable-vapigen
>>> autoreconf: Entering directory `.'
>>> autoreconf: configure.ac: not using Gettext
>>> autoreconf: running: aclocal -I m4
>>> autoreconf: configure.ac: tracing
>>> autoreconf: running: libtoolize --copy
>>> autoreconf: running: /usr/bin/autoconf
>>> autoreconf: running: /usr/bin/autoheader
>>> autoreconf: running: automake --add-missing --copy --no-force
>>> autoreconf: Leaving directory `.'
>>> configure: WARNING: unrecognized options: --disable-vapigen
Not I'm starting to test only rollingback that checkin.
regards
2014-09-16 10:14 GMT+02:00 Luca Bruno <lethalma...@gmail.com>:
> On 15/09/2014 14:50, Michele Dionisio wrote:
> > It is not possible any more to cross-compile vala after commit
> >
> > 797a15747b7c0cb43ea7e13687f1af34f6e14ddf build: Avoid using ".." for
> > referencing paths and reorganize valac-calls
> > 7a4f0befbd58286a69367ba78d16187da25724f7 build: Make building vapigen
> > non-optional
> >
> > because the builded vala is used during compilation. But If I'm
> > crosscomplling I cannot use the builded vala because I'n not on the
> target
> > machine.
> About the vapigen thing, you can still disable it from the configure.
> _______________________________________________
> vala-list mailing list
> vala-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/vala-list
>
_______________________________________________
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list
