<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 12-01-29 10:38 AM, J Habib wrote:
<blockquote
cite="mid:1327851480.72509.YahooMailNeo@web161906.mail.bf1.yahoo.com"
type="cite">
<div style="color:#000; background-color:#fff; font-family:times
new roman, new york, times, serif;font-size:12pt">
<div>Hello Team<br>
<br>
I want to use xdotool for simulating click and touch on a
MeeGo-based IVI device (Target).<br>
<br>
I downloaded the xdotool from
<a class="moz-txt-link-freetext" href="http://www.semicomplete.com/projects/xdotool/">http://www.semicomplete.com/projects/xdotool/</a> and the
pre-requisite libraries: libX11-1.4.4.tar.bz2 and
libXtst-1.2.0.tar.bz2 from
<a class="moz-txt-link-freetext" href="http://xorg.freedesktop.org/releases/individual/lib/">http://xorg.freedesktop.org/releases/individual/lib/</a> but I am
not able to install the pre-requisite libraries on MeeGo using
the config and makefiles provided with the package. Also
zypper install xdotool or pkcon install xdotool on MeeGo
Target is not able to fetch the xdotool as it is not available
for MeeGo repository.<br>
<br>
Please find below the list of errors displayed while
configuring & make (libX11-1.4.4.tar.bz2):<br>
<br>
./configure<br>
<br>
checking keysym definitions... configure: error cannot find
keysymdef.h<br>
<br>
After providing the above header path in configure file
(commenting the line 14262 and providing the hardcoded path at
14263), the following error is displayed on configure:<br>
<br>
checking keysym definitions... ./configure: line 14488: syntax
error near unexpected token '(' <br>
./configure: line 14488: `$ac_echo_n "(cached)" >&6`<br>
<br>
make:</div>
<div>make: *** No targets specified and no makefile found. Stop
<br>
</div>
<div>(The above is probably because config is not complete)</div>
<div><br>
</div>
<div>make -f Makefile.am</div>
<div>Makefile.am:1:***missing separator. Stop</div>
<div><br>
</div>
<div>Could you please provide the info on or direct me to the
concerned team for providing info on how to proceed for
installation of xdotool on MeeGo and/or from where should I
download the compatible xdotool and the pre-requisite
libraries if the above are not compatible with MeeGo.<br>
</div>
<div><br>
</div>
<div>Thanks</div>
<div><br>
</div>
<div>J Habib</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
<a class="moz-txt-link-abbreviated" href="mailto:xorg-devel@lists.x.org:">xorg-devel@lists.x.org:</a> X.Org development
Archives: <a class="moz-txt-link-freetext" href="http://lists.x.org/archives/xorg-devel">http://lists.x.org/archives/xorg-devel</a>
Info: <a class="moz-txt-link-freetext" href="http://lists.x.org/mailman/listinfo/xorg-devel">http://lists.x.org/mailman/listinfo/xorg-devel</a>
</pre>
</blockquote>
<br>
If you look in libX11 configure.ac,<br>
<blockquote><tt># Always required</tt><br>
<tt>X11_REQUIRES='xproto >= 7.0.17 xextproto xtrans xcb >=
1.1.92'</tt><br>
<tt>X11_EXTRA_DEPS="xcb >= 1.1.92"</tt><br>
</blockquote>
these are the packages (and probably some more) you need to build
libX11. Those packages in turn may need other packages to build.
Unfortunately, the presence of these packages are checked *after*
the check for keysymdef.h from the "xproto" package.<br>
<br>
A good place to look for dependencies is in each package .pc file.
Look for "Requires" variable for a hint on the prereqs.<br>
<br>
The method you are using, building from source starting at an
arbitrary point, will eventually work but it is a long road. You
might look in your OS packages for some X development libraries and
headers which would give you a head start.<br>
<br>
Note that when you run ./configure, the default installation
directory is rooted at /usr/local or /usr depending on your
platform. When running 'make install', you must have root
permission, else if will fail to install binaries or headers which
will cause subsequent packages to fail. Look for an S["prefix"]=
string in config.status to find the exact value.<br>
<br>
You may not have noticed, but you were able to run ./configure that
far because there is an xorg-macros package already installed on
your box. Running pkg-config --print-errors --variable=prefix
xorg-macros will tell you where.<br>
<br>
Now you have little choice but to ./configure --prefix <where
ever the rest is already installed>.<br>
<br>
This wiki might help:
<a class="moz-txt-link-freetext" href="http://www.x.org/wiki/ModularDevelopersGuide#Building_Individual_Modules_Yourself">http://www.x.org/wiki/ModularDevelopersGuide#Building_Individual_Modules_Yourself</a><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>