public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: "Bruce Dobrin" <dobrin@imageworks.com> To: <cygwin-xfree@cygwin.com> Subject: XInputExtension Date: Tue, 03 Feb 2004 21:48:00 -0000 [thread overview] Message-ID: <00a701c3ea9f$52e9f5b0$4d1f1cac@THEODOLITE> (raw) In-Reply-To: <20040203083050.65196.qmail@web15203.mail.bjs.yahoo.com> Hello, I've been trying to get some apps to work in X11 on windows, but have been getting errors having to do with input extension module XInputExtension. Is this unsupported? Partially supported? other? I checked the setup and apparently the imake cf file for cygwin does imply that there is some support: cygwin.cf -----------------------snip----------------- #define BuildGlxExt YES #define BuildXInputExt YES /*<<<<<<<<<<<<<<<<<<*/ #define BuildXF86VidModeExt NO #define BuildXF86DGA NO /* No direct access to hardware */ -----------------------snip------------------------- I also tryied putting this by hand into the site.def. It appears that it was compiled in : dobrin@THEODOLITE:/c/temp/xfree86.3.0/xc/exports/bin> grep XInputExten * Binary file cygXi-6.dll matches Binary file cygXtst-6.dll matches ... Binary file lib/Xi/XExtInt.o matches ..... Binary file programs/Xserver/XWin.exe matches We tryed to add a module loading section to the XF86config file, but it doesn't indicate that that is supported and the it also doesn't appear to work. xdpyinfo indicates the same 22 extensions regardless of changes to the XF86config file. /tmp/XWinrl logs do not appear to have anything relevent. Help!? thanks Bruce Dobrin Imageworks.com
prev parent reply other threads:[~2004-02-03 21:48 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-02-03 8:31 xedit failed with core dump victor zhang 2004-02-03 21:48 ` Bruce Dobrin [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='00a701c3ea9f$52e9f5b0$4d1f1cac@THEODOLITE' \ --to=dobrin@imageworks.com \ --cc=cygwin-xfree@cygwin.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).