linking

Chuck Robey chuckr at telenix.org
Sun Jul 27 10:01:09 PDT 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've rewritten this at least 4 times, I don't want it to be accusatory.  I've
gotten my test jig "cpconfig" to link, and used it to show me how the conf
functions in the parser/ directory work to access the data in the xorg.conf
file.  I made a "testmake" makefile that allows me to easily build & rebuild
cpconfig while using any function I want in the parser/ directory.

My problem is admittedly minor: I would really rather read the Xorg xserver's
idea of the configure state, but if one tries to link in anything from the
common/ directory, the gross interdependency of all of those object files means
you have to bring in every object from the entire Xorg, in order to test one
function.  Because I can't find any docs on how to use the funcs I found in
driver/xf86-input-mouse/src/mouse.c, and I can't link together a test jig, I am
now forced to use the things I CAN test (from parser).  No docs there either,
but being able to use gdb to trace things makes up nicely for that(I feel at
home enough with gdb).

Isn't there any way to test the config things I found in mouse.c?  Or, isn't
there any documentation  on the functions (details like all of the inputs and
outputs?)  If I can't derive, somehow, that info, I'll be forced to read the
xorg.conf for my info.

At least, now, I finally have a road to finishing my Xinput driver, and my code
is getting written, finally.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkiMqdUACgkQz62J6PPcoOkp3ACgoWWbmh+gnDBvJ0gnTTQ/km2I
WeMAn2e4aDE6iwDbqeiYotsdAYFflgPU
=pTqe
-----END PGP SIGNATURE-----



More information about the xorg mailing list