Will Steve Holmes wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Wow, it's a miricle my system runs at all then.:) I got most of that order totally backwards. <hmmm> the next time some updates appear in svn, I'll reverse my build order. I like having the improvements in accessibility and I thought I heard that 2.20 branch wasn't getting as many of these fixes. Well, my steak dinner tastes much better now than it did on Friday night when I was being relegated to eating a peanut butter sandwich..) On Mon, Jan 28, 2008 at 08:45:23AM -0500, Willie Walker wrote:Hi Sebastien:The 'official' word (i.e., from me ;-)) is that Orca is supported on the version of GNOME that it ships with. So, Orca 2.20.x is for GNOME 2.20.x, and Orca 2.21.x is for GNOME 2.21.x, etc.The unofficial word for is that you can use Orca 2.21.x on a GNOME 2.20.x system just fine, but you need to build/install extra stuff as you indicate below. The order of the building depends upon the order of the dependencies. Here's how I remember the order:1) The AT-SPI defines the overall API and provides the overall support for the infrastructure, so at-spi need to be built first.2) The ATK provides the generic layer for toolkits to use the infrastructure, so the atk needs to be built second.3) GAIL uses ATK to provide AT-SPI support for GTK+, so it needs to be built after ATK and AT-SPI4) Orca depends upon all the above. Hope this helps, WillPS - I just updated http://live.gnome.org/Orca/DownloadInstall to include the right order.On Jan 28, 2008, at 4:17 AM, Sébastien Hinderer wrote:Dear Steve, Many, many thanks for your reply. It will definitely be helpful.The best way to get there would be to go to http://live.gnome.org/Orca/FirefoxThanks. I already followed the instructions on the DownloadInstall page of Orca's wiki. So the question is more like: which components of gnome should be recompiled rom sources ?and read down to the links that discuss updating Orca. This documentation stresses the importance of updating at-spi and Orca with svn (subversion) but once going through there, you will soon realize you need to update atk as well. I've seen on list here that gail is kept to current svn levels too. So in summary, you would svn gail from gnome's svn, build it, install it and then proceed to atk and do the same. After that, build and install at-spi per the directions given at the Orca wiki and finally Orca itself.Okay so you recommend a four-steps procedure which consists in compiling/installing 1. gail 2. atk 3. at-spi 4. orcaIs it correct that this procedure _won't_ update the whole gnome desktopfrom the debian-packaged version 2.20 to the development version 2.22 ?My understanding was that that it's really important to update the wholegnome desktop. Is that true or will the previous procedure be enough ? Thanks for helping, Sébastien. _______________________________________________ Orca-list mailing list Orca-list gnome org http://mail.gnome.org/mailman/listinfo/orca-list Visit http://live.gnome.org/Orca for more information on Orca_______________________________________________ Orca-list mailing list Orca-list gnome org http://mail.gnome.org/mailman/listinfo/orca-list Visit http://live.gnome.org/Orca for more information on Orca- -- HolmesGrown SolutionsThe best solutions for the best price! http://holmesgrown.ld.net/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHnfD7WSjv55S0LfERAxgOAJ9UTVSDfpFfaLzy3YLaYZrU5LYe7wCdG6Rn bBo2B25hJ2dVyhAjUnllIag= =MqM5 -----END PGP SIGNATURE----- _______________________________________________ Orca-list mailing list Orca-list gnome org http://mail.gnome.org/mailman/listinfo/orca-list Visit http://live.gnome.org/Orca for more information on Orca