Grx June 2003

grx@gnu.de

7 participants
18 discussions

mingw DLL support
by Dimitar Zhekov 09 Jun '03

09 Jun '03

Hi. I ported GRX to lcc-win32, overcoming all it's (lcc-win32's, no offence) bugs somehow, but wasn't happy with the results: -O (optimize) generated invalid code. Anyway, I gained some experience and was able to write DLL support for the MinGW version of the library. How it works: 1. The MinGW section of makedefs.grx contains a new setting, "USE_DYNAMIC". When set to 'y', all sources are compiled with -D__DLL32__ and src/makefile.w32 creates/installs/etc. a DLL and an import library instead of a static library. 2. <grx20.h> and <libbcc.h> define "extern", if not already defined, to "extern __declspec(dllimport)" if __DLL32__ is defined and to "extern" if not just before the first public symbol, and undefine it after the last public symbol. 3. The private headers (<libgrx.h>/<bccgrx00.h>/...) define "extern" to "extern" before including <grx20.h>/<libbcc.h>. 4. All GRX suorces include <grx20.h>/<libbcc.h> not directly but via a private header [14 changes] and include <libgrx.h> before <grdriver.h>/<grfontdv.h>/<grxkeys.h> [1 change]. It sounds more compilated than it is. In a few words, the exported public symbols are seen as "extern" by the library and as "extern __declspec(dllimport)" by the applications. 5. If the DLL is being detached and the window thread is still [indicated as] running, the GRX window is closed. All symbols from <grx20.h> and <bccgrx.h> are exported; the symbols private to GRX are exported because of their macro usage (mostly when GRX_SKIP_INLINES is not defined). _GrCloseVideoDriver is exported solely because of demogrx. To use the DLL version of the library, simply recompile your application with "-D__DLL32__". The DLL is 341KB, the test programs are (average) 16KB; demogrx is 24KB; bccbgi is 37KB (all executables stripped). The overhead of using a DLL is significant when doing many calls to small GRX functions, such as get/put pixel, and negligible for complex functions. The DLL is stable. If anything is improperly declared inside libgrx, either the assembler fails because of duplicate "_D" symbols, or the DLL doesn't link because of missing "__imp_" symbols. That is, you can't have an invalid DLL. All tests run as supposed and the changes aren't big, so IMHO the DLL support is worth including in the 2.4.6 release. Mariano? P.S. <bgiext.h> is emptied, it does the same as <libbcc.h>. P.P.S. Non-incremential, as far as my patches are concerned. -- E-gards: Jimmy

1 0

DBGPRINTF() GrKey*() removal-q
by Dimitar Zhekov 05 Jun '03

05 Jun '03

Hi. >From utils/dbgprint.c: 40:void _GR_debug_printf(char *fmt,...) ... 56:#ifndef __XWIN__ 57: if (GrKeyPressed()) { 58: if (GrKeyRead() == GrKey_Escape) exit(1); 59: } 60:#endif Can we please remove this? There are many calls to DBGPRINTF() before the video driver is initialized, and in these calls the invokation of GrKeyPressed()/GrKeyRead() attempts to initialize the input driver, which is generally impossible if the video driver is not yet initialized. As a result, this code fails on X11 and Win32 (InitializeCriticalSection() is never called => "invalid page fault in module KERNEL32.DLL"), and on svgalib the GrKeyPressed() call acts as GrKeyRead() before video the init. By removing this we will also be able to remove the linking of any programs that call GRX functions but have no video output against the underlying graphics libraries. For example, fnt2c is linked with -lvga (or -X11, or whatever) only because it's debug version requires the input driver, which requires the video driver, which in turn requires the graphics libraries. That is, we'll at last be able to separate the different UTILP* programs. BTW, the MinGW Win32 DEBUG version of fntc2 still doesn't link because of this issue: it's link command lacks -lwindows -lconsole. Not that is works. Thus, instead of making the debugging more comfortable, this code actually breaks the debugging functionality on some (all but MSDOS?) platforms. E-gards: Jimmy

2 1

bccbgi textio fix
by Dimitar Zhekov 05 Jun '03

05 Jun '03

Hi. The GRX raw keyboard I/O can't be safely used in text mode. I fixed the examples some time ago, but forgot test/bgi/. -- E-gards: Jimmy

1 0

GRX 2.4.6 pre-release 4
by Mariano Alvarez Fernandez 03 Jun '03

03 Jun '03

Hi, I have uploaded a new pre-release of GRX 2.4.6. I plan to make it the final 2.4.6 if no big problems are reported. http://grx.gnu.de/more.html Enjoy, M.Alvarez

3 5

GRX on WinXP
by Waldemar Schultz 02 Jun '03

02 Jun '03

hello GRX guys, I tried to use GRX with DJGPP (both from the latest DJ-ZIP-picker). It compiled fine, but the demogrx program (in a WinXP cmd box) just blanks the screen and nothing else. I tried GRX20DRV=VESA and GRX20DRV=<empty>. Is this a known issue or a mistake of mine? Thank you for any advice. -- Gruss Waldemar Schultz. schultz(a)ma.tum.de Technische Universität München Zentrum Mathematik M1, D 85748 Garching Tel: +49 (0)89 28 91 79 36 FAX: +49 (0)89 28 91 79 32

2 1

win fonts name/family etc.
by Dimitar Zhekov 02 Jun '03

02 Jun '03

Hi. Some windows resource font driver changes: - better name/family support - avoid possible family buffer overflow - any character compared against EOF must be int - sprintf(hdr->name, ...) is safe, the longest family is 10 chars Also, I'm about to implement lcc-win32 support instead of the (abandoned?) Watcom real mode, remove the GRX private definition of alloca() for Turbo C (is has working alloca() from 10 years now) and the related stuff, and remove the obsolete near/far/huge keywords stuff (we support the real mode in large model only, don't we?), except for the 8086 Turbo C assembler code. But that will be after 2.4.6, of course. RFC. -- E-gards: Jimmy

2 1

Makefile and configure updates
by Guillem Jover 02 Jun '03

02 Jun '03

Hi, I've been thinking on packaging grx for Debian. I don't know if I'll do that but anyway, as I have been using it for some projects I've some updates to the library. This patch updates the configure and some makefiles, it uses now standard GNU configure paths, overrideable with the configure script, or make variables. It honours DESTDIR, and makes easier the packaging task. HTH, guillem

3 3

Wrong Texinfo filename and translated helper program
by Guillem Jover 02 Jun '03

02 Jun '03

Hi, Attached a patch that corrects the version of the texinfo file. Also I've translated the soruce code of ex2tex.c to english. And included a makefile for unices. HTH, guillem

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

Grx June 2003