Open tudo75 opened 3 years ago
The headers are included in the dev package already, but installed into a "xed" subdir, e.g. /usr/include/xed/xed-app.h
. You can verify this using apt-file list xed-dev
.
So you need to either #include <xed/xed-app.h>
or add this directory to you include path. I can't help you with you Vala issue though as I haven't used Vala yet.
As you can see I solved adding the folder taken from the manual building of Xed. Vala wants an entry point header with the same name of the package from which create the vapi files that expose the xed api. And also some header created on the fly during the build that there aren't in the dev package. Not a big issue due to the fact that working only on an LTS release there is only one version of the app.
Thanks for all
PS: my next step is to create a debian package of all my vala plugins, but it's the first time and there are a lot of things that I don't know so I need time to try and learn how to achieve that
Issue I'm not sure if this it's the right place to address this issue. I ported the codecomment plugin from Gedit to Xed writing it in Vala https://github.com/tudo75/xed-codecomment-plugin I installed xed-dev package but I noticed some headers, that are created at compilation time, are missing (you can find them here) from the package and also miss the Xed-1.0.h that it's needed for Vala development as start point (Vala search for an header with the same name of the gir package). I must compile Xed myself to have these files and from there I was able to create the vapi files needed to Vala to know the library structure.
So maybe will be a good thing integrate all these files in the dev package to simplify also the integration of my, and hopefully made by others, Vala plugins. My next try will be to port the highly asked session-saver plugin
Bye