From kde-accessibility Sat Nov 10 20:56:09 2018 From: Frederik Gladhorn Date: Sat, 10 Nov 2018 20:56:09 +0000 To: kde-accessibility Subject: Re: libqaccessibilityclient Message-Id: <2295294.4FoHd2eyWj () lumpi> X-MARC-Message: https://marc.info/?l=kde-accessibility&m=154188339930680 Hi Chrys, On l=F8rdag 10. november 2018 18:02:57 CET chrys wrote: > Howdy, >=20 > i just tired to compile git and got an error, any idea? seems to be an > dated make script: Generally with cmake, I'd recommend creating a separate build dir. I think you ran cmake src/ which would be interpreted as just using the src= =20 sub dir as the top level project dir. Try for example: cd libqaccessibilityclient mkdir build cd build cmake .. make I hope that works! Cheers, =46rederik >=20 >=20 > 17:53 [chrys@blackbeast libqa11y] :( $ git clone > https://github.com/KDE/libqaccessibilityclient.git > Klone nach 'libqaccessibilityclient' ... > remote: Enumerating objects: 2135, done. > remote: Total 2135 (delta 0), reused 0 (delta 0), pack-reused 2135 > Empfange Objekte: 100% (2135/2135), 376.96 KiB | 56.00 KiB/s, Fertig. > L=F6se Unterschiede auf: 100% (1656/1656), Fertig. >=20 > 17:54 [chrys@blackbeast libqa11y] :) $ cd libqaccessibilityclient/ >=20 > 17:54 [chrys@blackbeast libqaccessibilityclient] master :) $ ls > AUTHORS COPYING Mainpage.dox src/ > ChangeLog docs/ QAccessibilityClientConfig.cmake.in tests/ > CMakeLists.txt examples/ README >=20 > 17:54 [chrys@blackbeast libqaccessibilityclient] master :) $ cmake src/ > -DCMAKE_INSTALL_PREFIX=3D/usr > -- The C compiler identification is GNU 8.2.1 > -- The CXX compiler identification is GNU 8.2.1 > -- Check for working C compiler: /usr/bin/cc > -- Check for working C compiler: /usr/bin/cc -- works > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Detecting C compile features > -- Detecting C compile features - done > -- Check for working CXX compiler: /usr/bin/c++ > -- Check for working CXX compiler: /usr/bin/c++ -- works > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Detecting CXX compile features > -- Detecting CXX compile features - done > CMake Error at CMakeLists.txt:23 (target_link_libraries): > target_link_libraries called with incorrect number of arguments >=20 >=20 > CMake Error at CMakeLists.txt:33 (install): > install EXPORT given no DESTINATION! >=20 >=20 > CMake Warning (dev) in CMakeLists.txt: > No cmake_minimum_required command is present. A line of code such as >=20 > cmake_minimum_required(VERSION 3.12) >=20 > should be added at the top of the file. The version specified may be > lower > if you wish to support older CMake versions for this project. For more > information run "cmake --help-policy CMP0000". > This warning is for project developers. Use -Wno-dev to suppress it. >=20 > -- Configuring incomplete, errors occurred! > See also > "/home/chrys/Build/libqa11y/libqaccessibilityclient/CMakeFiles/CMakeOutpu= t.l > og". 17:54 [chrys@blackbeast libqaccessibilityclient] master :( $ > 17:55 [chrys@blackbeast libqaccessibilityclient] master :( $ > 17:55 [chrys@blackbeast libqaccessibilityclient] master :( $ cmake > Usage >=20 > cmake [options] > cmake [options] >=20 > Specify a source directory to (re-)generate a build system for it in the > current working directory. Specify an existing build directory to > re-generate its build system. >=20 > Run 'cmake --help' for more information. >=20 > Am 07.11.18 um 13:44 schrieb chrys: > > Howdy Federik, > >=20 > > ow cool. I really want to take a look at. > >=20 > > is this the official clone address: > >=20 > > https://github.com/KDE/libqaccessibilityclient.git > >=20 > > we want to make an "git" PKGBUILD for ArchLnux for this. to be able to > > test more fast and bring the most recent technology to ArchLinux users > > for testing. > >=20 > > sounds very awesome since gnome accersiser is slow and buggy (and > > unmaintained?) in many ways. > >=20 > > you are doing so much great job, dont know how can i thank for all this. > >=20 > > I m a little in struggle with the focus handling of the Kickoff main > > menu. i will contact you there PM. > >=20 > > cheers chrys > >=20 > >> Hi all, > >>=20 > >> I was just asked to make a new release of libqaccessibilityclient. > >> I'm not sure if I'll get around to it any time soon, so I was wondering > >> if > >> anyone is interested. > >>=20 > >> Task: create a release - this means bumping the version number, doing a > >> clean git export and some other small task. If anyone is willing to do > >> this, I'll mentor happily. It's not very technical and should not take > >> very long either. But since I'm generally busy I don't want to > >> constantly be the blocker for all kinds of tasks. It's a nice way to g= et > >> started. > >>=20 > >>=20 > >> Now I guess you may wonder what this little gem is? > >> It's a library to deal with accessibility information from the client > >> point of view, such as Orca would. This means it can find which object > >> has the focus and similar stuff. I don't think the architecture is the > >> best it could be (it's doing a lot of synchronous dbus calls, so falls > >> into the same traps as most of the stack), but it's a start at least. > >>=20 > >> When debugging accessibility issues it's nice at least, it contains a > >> small > >> app that is similar to accerciser (and broken in different ways :P ). > >> Since I was looking at KWin I also added a small command line tool whi= ch > >> simply dumps the entire tree of accessible objects of any application, > >> the > >> code is here:https://phabricator.kde.org/D16634 (waiting for review, > >> maybe by Chrys). > >>=20 > >> Other uses are in KMag which can follow the keyboard focus with the > >> magnifier that way. Maybe we should consider if that's desirable for t= he > >> KWin effect also. > >>=20 > >> Simon (the speech recognition app) can use it as well to let the user > >> speak > >> various UI elements to trigger them. > >>=20 > >> Cheers, > >> Frederik