After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 750462 - Cannot compile without vapigen-0.26
Cannot compile without vapigen-0.26
Status: RESOLVED FIXED
Product: libgda
Classification: Other
Component: Vala bindings
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Daniel Espinosa
gnome-db Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-06-05 17:04 UTC by Gergely POLONKAI
Modified: 2015-06-05 19:49 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Gergely POLONKAI 2015-06-05 17:04:06 UTC
This is a “new version” of #678647 just the vapigen version has changed. Now it looks for vapigen-0.26. I have changed configure.ac to look for 0.28 and it seems to work fine.

According to vapigen.m4, you may omit the [0.28] part in which case it will look for “vapigen” (without any version numbers). If you leave the version number (currently 0.17.7) I think you will get the desired result (although you may want to consult a Vala guru on this).
Comment 1 Daniel Espinosa 2015-06-05 18:04:47 UTC
As for Debian 7, you have installed vapigen.pc and vapigen-0.26.pc files, then you can use both versioned and unversioned checks, the problem comes when you have both 0.26 and 0.28 versions installed. Then in some systems you have a "default" version set to 0.26 not 0.28 if you want to use it, when check for unversioned.

Because libgda install its bindings to unversioned directory, you will have bindings to be used for both 0.26 or 0.28 versions of Vala. In general this is not an issue because they are almost compatible but is not a warranty.

If some one have a Fedora or Ubuntu box, we can check if you have both versioned and unversioned installed. AFAIR you have to use versioned checks in order to detect correctly installed pc file.

One action to take could be to update version to 0.28, because it is the current stable Vala's version, is present in resent distributions and libgda is not released yet, when it will may be we will have 0.28 available.

But in the future when libgda is released we will be at 0.30 for Vala, then you will have to install Vala-0.28 in order to compile libgda from sources.

Another is to add a directive --set-vala-version-to="VERSION" in order to help future packagers to distribute libgda with the current vala version in use and then install versioned Vala bindings. This just requires to check if libgda compiles with the version packager wants to compile against.

Unless other have any comment here I go to change required Vala version to 0.28 and add support for --set-vala-version-to switch.
Comment 2 Gergely POLONKAI 2015-06-05 18:47:48 UTC
I’m actually on a Fedora box (F22, recently upgraded), and I can only install a vala-tools package, which provides the vapigen and vapigen-0.28 binaries. I didn’t know it is possible to install several Vala versions as I haven’t tried it before, but in this case this --set-vala-version-to switch seems an ideal solution to me (maybe you should use --with-vala-version instead, though).
Comment 3 Daniel Espinosa 2015-06-05 19:30:41 UTC
Please check commit:

https://git.gnome.org/browse/libgda/commit/?id=9afeef02b2a55b260e9287fcceed39b9b14d391c


It adds support for environment variable to change default Vala package to check, now it defaults to 0.26 for easy backport to 5.2.x.

With it you can use set VALA_API_VERSION set to, i. e., 0.28 to check for vapigen-0.28, or in the future change it to required version. Use --enable-vala

If just --enable-vala is set and no environment variable, then defaults to check for vapigen-0.26 package.

Package to check should be at least 0.26.0.
Comment 4 Gergely POLONKAI 2015-06-05 19:41:55 UTC
This is very nice, thank you!
Comment 5 Daniel Espinosa 2015-06-05 19:49:44 UTC
Fixed. Closing.