Date:	Thu, 12 Jan 1995 08:08:45 +0500
From:	ld AT netrix DOT com
To:	djgpp AT sun DOT soe DOT clarkson DOT edu, Eric DOT Nicolas AT iota-eso DOT u-psud DOT fr
Subject:	Re: Questions... about gcc, libgrx, sword

> From djgpp-bounces AT sun DOT soe DOT clarkson DOT edu Thu Jan 12 07:57 EST 1995
> From: "Eric.Nicolas" <Eric DOT Nicolas AT iota-eso DOT u-psud DOT fr>
> Date: Thu, 12 Jan 95 13:03:03 CST
> X-Popmail-Charset: English
> To: djgpp AT sun DOT soe DOT clarkson DOT edu
> Subject: Questions... about gcc, libgrx, sword
> 
> I had several questions about gcc and libgrx
> 
> 1. When I compile and link a program with gcc, I am always able to run 
>    debug32 after this compilation. And debug32 is always able to find 
>    symbol table in my .OUT file.
>    So the question is : How can I remove those debug info from .OUT file, 

  strip <programname>

>    or how can I compile without produce those debug infos ?   

  remove the -g option on your gcc commandline

> 2. I use the libgrx library both with TurboC and GCC, and I have a problem
>    with the Mouse and Keyboard Event mechanism. I enabled both Mouse AND 
>    Keyboard events handling with interrupts. With TurboC, everything goes
>    well, but with GCC, keyboards entries simply stays in the BIOS's keyboard
>    buffer ! Does anyone have an explanation ?

  Did you write your own handler? If you did, try to add some realmode callback.

> 3. Is there someone in the net who lokked at SWORD GUI for TurboC and GCC ?
>    Please, if you looked, tell me what you thought.
>    You can find it at : omnigate.clarkson.edu
>                         /pub/msdos/djgpp/pub/
 

- Raw text -