nanogui@linuxhacker.org

Greg Haerr wrote:

> For building programs that don't include anything except the 
> exported Microwindows libraries, Jordan's idea will  work 
> well, except for ONE big problem:  Unfortunately, user programs
> need to know what the MWPF_PIXELFORMAT is that
> Microwindows was compiled with, in order for fast GrArea
> calls to work.  Also unfortunately, this #define is #if'd in the
> Microwindows header files for certain color macros... ;-(

You're bringing back memories from couple months ago. The first time I 
picked up Microwindows I was considering using it in a project that 
needed palette manipulation on a 16 color VGA card. So I was doing some 
hacking with the color defines and palette routines. That define 
MWPF_PIXELFORMAT was one of the problem areas.

I got to thinking today that another option to the "Makefiel.rules - 
Makefile.defs" approach would be to move the define macros, include 
directory macros, library macros, etc. into a section at the end of the 
config file, rather than making a new ".defs" file. That way application 
build scripts only have to point to the config file to find out how 
Microwindows was built.


Gary James