delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1998/09/07/23:58:23

To: djgpp AT delorie DOT com
Cc: oti AT phys DOT uu DOT nl
Subject: Re: XWinAllegro
References: <Pine DOT OSF DOT 3 DOT 95 DOT 980907144536 DOT 23461C-100000 AT ruunf0 DOT phys DOT uu DOT nl>
From: M DOT A DOT Bukin AT inp DOT nsk DOT su
Date: 08 Sep 1998 10:12:36 +0700
In-Reply-To: Elliott Oti's message of "Mon, 7 Sep 1998 12:50:38 GMT"
Message-ID: <20n28b1emz.fsf@Sky.inp.nsk.su>
Lines: 29

Elliott Oti <oti AT phys DOT uu DOT nl> writes:

> I have compiled XWinAllegro on a DEC Alpha running OSF 1.
> To my surprise (and pleasure) it compiled more or less out of the box
> (with only a few #defines), and all the demos work quite well. The
> major

  I'd like to know what changes you need for compiling XwinAllegro.
Please, send them to me at <bukinm AT inp DOT nsk DOT su>.

> problem is that the Allegro keyboard functions do not work, and I don't
> know why. I would like to know if anyone has compiled or used XWinAllegro,
> and what his experiences were, especially with the keyboard handler.

  I have tried it on Sun Solaris and keyboard works after configuring.

  Have you configured keyboard?  Run ./setup/xwkbdcfg.exe and follow
instructions it gives you.  You should have ./xwkeyboard.cfg now.
XwinAllegro can find this file in several places.  Standard
configuration directory hardcoded in library, directory pointed to by
ALLEGRO environment variable, directory from which program was run and
current working directory.  Move this file in one of these directories
and XwinAllegro will use it as keyboard configuration.

  If you still have problems, write to me privately and I will send
you some suggestions for debugging this problem.

-- 
Michael Bukin

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019