There's been some recent changes to where valac looks for vapis in recent releases, I believe to separate where standard distribution vapis are installed and vapis from other libraries. That's probably part of the problem you're seeing, but I'm not sure.
Either way, glad you got it worked out. -- Jim On Wed, Oct 27, 2010 at 3:46 PM, Richard B. Kreckel <[email protected]>wrote: > On 10/27/2010 02:53 PM, Jim Nelson wrote: > >> These are bindings problems. I suspect you have old .vapi files on your >> system somewhere that the Vala compiler is using. (These bindings >> changed a while back.) >> >> I would uninstall 0.10 and recursively scan your /usr directory for any >> remaining .vapi files. gexiv2 and Gee install VAPIs, so those should >> not be deleted, but any GDK or GLib vapis you see after that should be >> removed. Then reinstall 0.10.0. >> > > Thanks a lot! (You know, I'm totally new to vala and didn't even know that > declarations are in .vapi files.) > > It turned out that uninstalling Debian/sqeeze's valac package (this is > version 0.8.1) solved the problem. Shotwell compiled fine then and works > like a charm. > > What I find strange though is that the custom installation of vala 0.10.0 > picked up files from the system's vala package (glib-2.0.vapi, for > instance). Shouldn't vala know where to look for .vapi files? > > > -richy. > -- > Richard B. Kreckel > <http://www.ginac.de/~kreckel/ <http://www.ginac.de/%7Ekreckel/>> > _______________________________________________ > Shotwell mailing list > [email protected] > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
