I am trying to generate meson files for our project that has AutoVala in use: https://github.com/cromnix/pamac-classic

The CMake files work great and everything builds just fine. However the meson files don't work. This is the output I get when trying to build:

meson --prefix=/usr --sysconfdir=/etc
The Meson build system
Version: 0.43.0
Source dir: /home/cromer/Desktop/projects/pamac-classic/test
Build dir: /home/cromer/Desktop/projects/pamac-classic/test/build
Build type: native build

Meson encountered an error in file meson.build, line 252, column 0:
Assignment target must be an id.
cfg_pamac-installer = configuration_data()
^

A full log can be found at /home/cromer/Desktop/projects/pamac-classic/test/build/meson-logs/meson-log.txt

This is the generated meson.build file: https://gist.github.com/cromerc/38782d85b179410905382e5a0e8cb440

The CMake of the gedit plugin passes without any problems, but the Make fails with

[ 75%] Building C object src/CMakeFiles/AutovalaGeditPlugin.dir/valaplugin.c.o
/home/philipp/Programme/autovala/gedit_plugin/install/src/valaplugin.c:16:31: fatal error: gedit/gedit-panel.h: Datei oder Verzeichnis nicht gefunden
 #include <gedit/gedit-panel.h>
                               ^
compilation terminated.
make[2]: *** [src/CMakeFiles/AutovalaGeditPlugin.dir/valaplugin.c.o] Fehler 1
make[1]: *** [src/CMakeFiles/AutovalaGeditPlugin.dir/all] Fehler 2
make: *** [all] Fehler 2

Maybe there is some dependency missing in the CMake files? I'm running Ubuntu GNOME with programs from ppa:gnome3-team/gnome3, ppa:gnome3-team/gnome3-staging and ppa:ricotz/testing, so they should be fairly up to date.

while trying to use "make" which is the result of cmake produced by autovala compilation fails with fatal error: dbus/dbus-glib-lowlevel.h: no such file or directory.

although file /usr/include/dbus-1.0/dbus/dbus-glib-lowlevel.h exist (corresponding -dev packages installed).

vala project used act as a dbus client, not server.

Since autovala uses cmake/* files would be handy if they would be installed (/usr/share/autovala or whatever) during autovala installation and used by autovala (symlink or copy) in project directory during "autovala update" command.

This will remove code duplication and makes autovala usage much easier.

It would be nice to have a way to make symlinks during install. I think that there are 2 possible ways that this could be implemented. custom: target link symlink Basically take advantage of the already existing custom tag but instead of copying a file create a symlink.

or just a symlink tag: symlink: target link

Right now I do some ugly hacky stuff to get symlinks created during the install step, it would be nice if autovala had support for symlinks built in.

Autovala installs hicolor icons using wrong directory names like 16, 22, 24, 32 while the hicolor theme only looks for icons in directories with names like 16x16, 22x22, 24x24, 32x32 instead (see the index.theme file in /usr/share/icons/hicolor). This issue effectively renders the installed icons useless because they will never be found.

Additionally, I think it would be handy to have some control over icon destinations. Besides the mentioned subdirectory names (which can differ between themes) also being able to install icons in other themes than hicolor. For example, I need to ship icons for ubuntu-mono-dark and ubuntu-mono-light.

In my project I have client which uses 3rd party dbus service from vala. Right now I obtain corresponding .vala code through d-bus introspection:

call to "dbus-send --session --type=method_call --print-reply=literal --dest=... org.freedesktop.DBus.Introspectable.Introspect" and then calling to "vala-dbus-binding-tool --api-path="

Is there a way to automate this with autovala?

The gresource system (and glib-compile-resources) is a handy way of dealing with resources, including embedding them into your program.

When there's a .gresource.xml file is found, glib-compile-resources should be called and the resulting C/H files included in the compilation, and a basic VAPI generated for it.

Hi,

Yesterday I ran the autovale-generated CMake for my app within a prestine Fedora 22 vm install and noticed the icons not showing up. An simple update-icon-cache command was able to solve that. Apparently the install script did not run the command at the right time.

So after investigating when exacltly when the update command was called, I found the calls for all themes in one specific (seemingly random) location: /data/icons/hicolor/22x22/CMakeLists.txt (see contents below this message)

I suppose this is the cause of the problem, the update command seems to be called after having installed just a few icons of one theme, while other icons have yet to be installed...

If you need to do some deeper analysis I can e-mail you the full project source.

### CMakeLists automatically created with AutoVala
### Do not edit

install(FILES ${CMAKE_CURRENT_SOURCE_DIR}/myapp-connected.png DESTINATION ${CMAKE_INSTALL_DATAROOTDIR}/icons/hicolor/22x22/status/)
install(FILES ${CMAKE_CURRENT_SOURCE_DIR}/myapp-connecting-1.png DESTINATION ${CMAKE_INSTALL_DATAROOTDIR}/icons/hicolor/22x22/status/)
install(FILES ${CMAKE_CURRENT_SOURCE_DIR}/myapp-connecting-2.png DESTINATION ${CMAKE_INSTALL_DATAROOTDIR}/icons/hicolor/22x22/status/)
install(FILES ${CMAKE_CURRENT_SOURCE_DIR}/myapp-connecting-3.png DESTINATION ${CMAKE_INSTALL_DATAROOTDIR}/icons/hicolor/22x22/status/)
install(FILES ${CMAKE_CURRENT_SOURCE_DIR}/myapp-disconnected.png DESTINATION ${CMAKE_INSTALL_DATAROOTDIR}/icons/hicolor/22x22/status/)
install(FILES ${CMAKE_CURRENT_SOURCE_DIR}/myapp.png DESTINATION ${CMAKE_INSTALL_DATAROOTDIR}/icons/hicolor/22x22/apps/)
IF( NOT (${ICON_UPDATE} STREQUAL "OFF" ))
    install (CODE "execute_process ( COMMAND /usr/bin/gtk-update-icon-cache-3.0 -t ${CMAKE_INSTALL_PREFIX}/${CMAKE_INSTALL_DATAROOTDIR}/icons/gnome )" )
    install (CODE "execute_process ( COMMAND /usr/bin/gtk-update-icon-cache-3.0 -t ${CMAKE_INSTALL_PREFIX}/${CMAKE_INSTALL_DATAROOTDIR}/icons/hicolor )" )
    install (CODE "execute_process ( COMMAND /usr/bin/gtk-update-icon-cache-3.0 -t ${CMAKE_INSTALL_PREFIX}/${CMAKE_INSTALL_DATAROOTDIR}/icons/ubuntu-mono-dark )" )
    install (CODE "execute_process ( COMMAND /usr/bin/gtk-update-icon-cache-3.0 -t ${CMAKE_INSTALL_PREFIX}/${CMAKE_INSTALL_DATAROOTDIR}/icons/ubuntu-mono-light )" )
ENDIF()

When running autovala update I get this:

Updating project file
Warning: Trying to add twice the file src/pamac-tray/tray-appindicator.vala for translation
Warning: Trying to add twice the file src/pamac-tray/tray-gtk.vala for translation
Storing configuration in file /home/cromer/Desktop/projects/pamac-classic/pamac.avprj
Updating CMake files
Warning: Trying to add twice the file src/pamac-tray/tray-appindicator.vala for translation
Warning: Trying to add twice the file src/pamac-tray/tray-gtk.vala for translation
Updating Meson files
Warning: Trying to add twice the file src/pamac-tray/tray-appindicator.vala for translation
Warning: Trying to add twice the file src/pamac-tray/tray-gtk.vala for translation
Done

This is caused by doing translations that depend on a build flag:

if KDE_TRAY
translate: vala src/pamac-tray/tray-appindicator.vala
else
translate: vala src/pamac-tray/tray-gtk.vala
end

There are no problems when building, it builds correctly. Just kind of ugly that it spits out these warnings.

Hi again! So, it seems a regression of issue #52 has come up again. The plugin does not show up in the plugin preferences (v 3.18.2, arch linux).

However, if you cannot reproduce this, it's probably because my install is messed up. Lately I cannot get the gedit-code-assistance plugin to do anything (at least for Vala) in gedit. I should probably try on another machine..... Let me know if you have any insight.

Thanks again for a truly impressive piece of software :)

Hi, i have some request for the "autovala po" command, now the command executed to generate the pot file is; xgettext --from-code=UTF-8 -d wifi-qrcode -o wifi-qrcode.pot -p po --keyword='_' --add-comments=Translators -f po/POTFILES.in

can you add same options to the xgettext command with the relative tags in the avprj file? The options --> tags to add are the seguent:

1. --package-name= --> project_name (already existing in avrpj)
2. --package-version= --> version (already existing in avrpj)
3. --copyright-holder= --> po_copyright_holder
4. --msgid-bugs-address= --> po_msgid_bugs_address

to have a command like this and a more complete pot file:

xgettext --from-code=UTF-8 -d wifi-qrcode -o wifi-qrcode.pot -p po --keyword='_' --add-comments=Translators -f po/POTFILES.in --copyright-holder="Copyright Info" --package-name=wifi-qrcode --package-version=0.20 --msgid-bugs-address=www.mybugzilla.bug

The xgettext option are explained in this page: https://www.gnu.org/software/gettext/manual/html_node/xgettext-Invocation.html

thanks

I just noticed that the packages built with meson are installing CMakeLists.txt files into the package. After install I have this: /usr/share/doc/CMakeLists.txt /usr/share/pamac/CMakeLists.txt

It would be nice if the custom tag had a component to choose the correct directory for the files for both meson and cmake. For example right now I have these custom tags:

custom: data/dbus/org.pamac.system.conf ${CMAKE_INSTALL_SYSCONFDIR}/dbus-1/system.d
custom: data/dbus/org.pamac.user.service ${CMAKE_INSTALL_PREFIX}/${CMAKE_INSTALL_DATAROOTDIR}/dbus-1/services
custom: data/dbus/org.pamac.system.service ${CMAKE_INSTALL_PREFIX}/${CMAKE_INSTALL_DATAROOTDIR}/dbus-1/system-services
custom: data/systemd/pamac-system.service ${CMAKE_INSTALL_LIBDIR}/systemd/system
custom: data/systemd/pamac-cleancache.service ${CMAKE_INSTALL_LIBDIR}/systemd/system
custom: data/systemd/pamac-cleancache.timer ${CMAKE_INSTALL_LIBDIR}/systemd/system
custom: data/systemd/pamac-mirrorlist.service ${CMAKE_INSTALL_LIBDIR}/systemd/system
custom: data/systemd/pamac-mirrorlist.timer ${CMAKE_INSTALL_LIBDIR}/systemd/system
custom: data/polkit/org.pamac.policy ${CMAKE_INSTALL_PREFIX}/${CMAKE_INSTALL_DATAROOTDIR}/polkit-1/actions
custom: data/mime/x-alpm-package.xml ${CMAKE_INSTALL_PREFIX}/${CMAKE_INSTALL_DATAROOTDIR}/mime/packages

Naturally in meson this is broken since $CMAKE_INSTALL_DATAROOTDIR is not set.

My suggestion would be to change the custom tag to this:

custom: data/dbus/org.pamac.system.conf dbus-1/system.d sysconfdir
custom: data/dbus/org.pamac.user.service dbus-1/services datarootdir
custom: data/dbus/org.pamac.system.service dbus-1/system-services datarootdir
custom: data/systemd/pamac-system.service systemd/system libdir
custom: data/systemd/pamac-cleancache.service systemd/system libdir
custom: data/systemd/pamac-cleancache.timer systemd/system libdir
custom: data/systemd/pamac-mirrorlist.service systemd/system libdir
custom: data/systemd/pamac-mirrorlist.timer systemd/system libdir
custom: data/polkit/org.pamac.policy polkit-1/actions datarootdir
custom: data/mime/x-alpm-package.xml mime/packages datarootdir

By having 3 arguments to the custom tag we can choose where on the system the files get installed to. This will also allow prefix installs to work correctly. For example I am using DESTDIR="$pkgdir" in a pacman PKGBUILD, which means I need the custom tag to respect the DESTDIR for the installation.

For example sysconfdir would put the correct directory "$DESTDIR/$PREFIX/etc" into the cmake/meson directories.

Currently it is not possible to have conditional compilation with CMake style expressions. This doesnot allow for very important system checking (Linux, Windows or OSX). For example I cannot have if (CMAKE_HOST_SYSTEM_NAME STREQUAL "Linux") in my avprj. This is interpreted wrongly. I suggest that you leave expressions in parentheses as is instead of tokenizing them. Also is there any alternative way of currently doing it. As vala only supports boolean macro variables, I tried to do this if and add compile options (-D PLATFORM_LINUX) inside it