[Kde-accessibility] Getting atspi2 working at OpenSuse 12.1

Sebastian Sauer mail at dipe.org
Thu Mar 8 05:26:03 UTC 2012


While putting some notes together how to get started with the gsoc2012 
proposal for porting focus tracking to atspi2 I had to upgrade my 
devel-setup and made a small step-by-step list what I did. Now rather 
then sharing that only with my potential gsoc-student I think sharing it 
with everybody makes sense. here we go.

My setup is a fresh OpenSuse 12.1 running in a vmware-player 4 (I do 
most development in vm's this days if possible to protect my productive 
system).

1) In Opensuse 12.1 install libatspi0 and python-atspi and 
at-spi2-core-devel from the suse repositories. You may need to add some 
community-repositories to be able to do so.
2) Add a file ~/a11y with following content;
gconftool-2 --set /desktop/gnome/interface/at-spi-dbus --type bool true
gconftool-2 --set /desktop/gnome/interface/at-spi-corba --type bool false
export QT_ACCESSIBILITY=1
export GTK_MODULES=gail:atk-bridge
3) Start Konsole and "source ~/a11y". That konsole session is now ready 
for hacking :)
4) Start "qdbusviewer &" and in the search-field add "a11y". Very likely 
nothing will be shown since atspi isn't started yet.
5) Start atspi with "/usr/lib/at-spi2/at-spi2-registryd" and repeat 4. 
Now there should be a "org.a11yBus" at the session bus.
6) You need to upgrade your used Qt-version to 4.8. Use Yast for that 
(repository is 
http://download.opensuse.org/repositories/KDE:/Qt/openSUSE_12.1/ ).
7) Install qt-atspi by building it from the sources ( 
http://gitorious.org/qt-at-spi ). Do not use distributor packages since 
they are outdated! For compile-instruction see also 
http://techbase.kde.org/Development/Tutorials/Accessibility/Screen_Reader_Setup#How_to_test_at-spi2_with_Qt
8) For testing execute those "tst_qt-atspi" program that is shipped with 
qt-at-spi. If everything wents fine you have now a full devel setup :)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-accessibility/attachments/20120308/daeb661b/attachment.html>


More information about the kde-accessibility mailing list