Re: [Vala] Debugging the compiler command generated by valac
Joe, Valac doesn't generate the compiler command. That along with all the include directories are figured out by the Cmake files in the case of Shotwell. — Sent from Mailbox for iPhone On Thu, Dec 26, 2013 at 11:58 AM, Joe Sapp nixpho...@gmail.com wrote: I'm having an issue with the C compiler command generated by valac. Specifically, an include directory is being included unexpectedly (see [1]). Is there any way to figure out what causes this to happen, or which package or file is at fault? I can't seem to find any way to get intermediate information between the `valac` call and the `cc` call. -- Thanks, Joe Sapp [1] https://bugs.gentoo.org/show_bug.cgi?id=492480#c5 ___ 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
[Vala] VAPI tutorial
Hi all: I wrote a little VAPI writing tutorial to help people to start writing VAPI files for libraries. I put it at https://wiki.gnome.org/Projects/Vala/WrittingVAPIs Of course it is incomplete, and is possible that it has mistakes, so I accept all kind of suggestions and fixes. -- Nos leemos RASTER(Linux user #228804) ras...@rastersoft.com http://www.rastersoft.com ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list
Re: [Vala] VAPI tutorial
There's a short section on VAPIs in the tutorial if I remember correctly. Would probably be helpful to link to this from there if you haven't already. — Sent from Mailbox for iPhone On Fri, Dec 27, 2013 at 6:43 PM, rastersoft ras...@rastersoft.com wrote: Hi all: I wrote a little VAPI writing tutorial to help people to start writing VAPI files for libraries. I put it at https://wiki.gnome.org/Projects/Vala/WrittingVAPIs Of course it is incomplete, and is possible that it has mistakes, so I accept all kind of suggestions and fixes. -- Nos leemos RASTER(Linux user #228804) ras...@rastersoft.com http://www.rastersoft.com ___ 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
Re: [Vala] VAPI tutorial
Probably best to link to the legacy VAPI guide: https://wiki.gnome.org/Projects/Vala/LegacyBindings On 27 December 2013 15:43, rastersoft ras...@rastersoft.com wrote: Hi all: I wrote a little VAPI writing tutorial to help people to start writing VAPI files for libraries. I put it at https://wiki.gnome.org/Projects/Vala/WrittingVAPIs Of course it is incomplete, and is possible that it has mistakes, so I accept all kind of suggestions and fixes. -- Nos leemos RASTER(Linux user #228804) ras...@rastersoft.com http://www.rastersoft.com ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list -- --Andre Masellaan...@masella.name http://www.masella.name/ ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list
Re: [Vala] VAPI tutorial
On Sat, 2013-12-28 at 00:43 +0100, rastersoft wrote: Hi all: I wrote a little VAPI writing tutorial to help people to start writing VAPI files for libraries. I put it at https://wiki.gnome.org/Projects/Vala/WrittingVAPIs Of course it is incomplete, and is possible that it has mistakes, so I accept all kind of suggestions and fixes. Seems like a duplicate of https://wiki.gnome.org/Projects/Vala/LegacyBindings I hope you'll consider merging what you've written into the other page. Meanwhile, I've added a note to WrittingVAPIs (which, BTW, is misspelled —writing only has one 't'). I haven't read what you posted yet, but on a quick skim I noticed that you are encouraging people to use ref_function=, unref_function=... instead of just free_function=... for a compact class. This is almost never the right thing to do since it will prevent Vala from properly managing the memory. In general, you might want to avoid using Xcb as an example since it's generally not a very good VAPI (though your recent changes do improve things quite a bit). -Evan ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list
Re: [Vala] Debugging the compiler command generated by valac
On Thu, 2013-12-26 at 11:58 -0500, Joe Sapp wrote: I'm having an issue with the C compiler command generated by valac. Specifically, an include directory is being included unexpectedly (see [1]). Is there any way to figure out what causes this to happen, or which package or file is at fault? I can't seem to find any way to get intermediate information between the `valac` call and the `cc` call. There are really only two pieces of information which are relevant—the generated C (which, in this case, is saved thanks to passing --save-temps to valac) and the arguments passed to cc. Most build systems keep the valac and cc invocations separate, but Shotwell rolled their own and chose not to do that, so the easiest way to see that information would probably be just running the valac command yourself, but pass --cc=echo. It looks like the problematic valac invocation is on lines 100-106 of that build log. That said, you probably don't really need to. One of these packages is adding the gee-1.0 include directory, probably through a (possibly indirect) dependency on gee-1.0: * shotwell-plugin-dev-1.0 * gobject-2.0 * glib-2.0 * gdk-3.0 * gtk+-3.0 * gee-0.8 * gtk+-3.0 * libsoup-2.4 * libxml-2.0 * webkitgtk-3.0 * gexiv2 * rest-0.7 * gee-0.8 * json-glib-1.0 If you can't find the dependency in the pkg-config file (a `pkg-config --cflags shotwell-plugin-dev-1.0 gobject-2.0 glib-2.0 ...` should tell you) for those libraries, look at the *.deps file next to the *.vapi— those libraries will also be included. If I were you I would first look at gexiv2 and shotwell-plugin-dev-1.0, since the others are pretty well tested on other platforms. -Evan ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list